You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A minimalist approach would be to rename the GitHub repository to hetio/hetiopy. A maximalist approach would be to rename all three locations to hetnetpy. I think hetnetpy works well with hetmatpy, although perhaps the visual similar is too high for easy disambiguation?
I'd go with whatever's more accurate. hetiopy isn't that much further from hetmatpy than hetnetpy is. hetnetpy probably is the way to go, and renaming all the location of it for clarity and consistency.
In d88f81a, I made it so users of v0.3.0 can still import hetio, but they get a warning:
>>> import hetio
/home/dhimmel/Documents/repos/hetio/hetio/__init__.py:11: FutureWarning: The 'hetio' package has been renamed to 'hetnetpy'. Future versions will remove the ability to 'import hetio'. Switch to 'import hetnetpy'.
warnings.warn(message, FutureWarning)
Activity
dhimmel commentedon Jun 11, 2019
Yeah this package was named a long time ago when only https://het.io and this package existed. Hence, I gave it the name
hetio.There are three main places where a software package has a name:
import hetioA minimalist approach would be to rename the GitHub repository to
hetio/hetiopy. A maximalist approach would be to rename all three locations tohetnetpy. I thinkhetnetpyworks well withhetmatpy, although perhaps the visual similar is too high for easy disambiguation?vincerubinetti commentedon Jun 11, 2019
I'd go with whatever's more accurate.
hetiopyisn't that much further fromhetmatpythanhetnetpyis.hetnetpyprobably is the way to go, and renaming all the location of it for clarity and consistency.dhimmel commentedon Jun 24, 2019
I'm having trouble finding good documentation on how to go about the renaming of the PyPI package. I am thinking that we could do the following steps:
__init__.pythat future versions of the package will be namedhetnetpy.hetnetpydhimmel commentedon Jul 10, 2019
References:
release v0.2.11 to warn about future rename to hetnetpy
[-]Rename this software[/-][+]Rename this software to hetnetpy[/+]Rename codebase to use hetnetpy from hetio
dhimmel commentedon Jul 10, 2019
Done! I think...
https://pypi.org/project/hetnetpy/
https://github.com/hetio/hetnetpy
In d88f81a, I made it so users of v0.3.0 can still
import hetio, but they get a warning: