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
The versioning mechanism in setup.py sets version to "Undefined", then does an exec() from init.py to get the version number from inside the file. Presumably this was done to have the version number appear in only one place, and it must have worked for PYPI the last time the package was distributed. Unfortunately, it breaks the rules for pip installs direct from the repo, as the exec never gets done. This really matters for those of us working from a PR like the one to do v2 search.
I believe the recommended way to do it is to put the static version in the package declaration and use importlib inside the module.
The text was updated successfully, but these errors were encountered:
The versioning mechanism in setup.py sets version to "Undefined", then does an exec() from init.py to get the version number from inside the file. Presumably this was done to have the version number appear in only one place, and it must have worked for PYPI the last time the package was distributed. Unfortunately, it breaks the rules for pip installs direct from the repo, as the exec never gets done. This really matters for those of us working from a PR like the one to do v2 search.
I believe the recommended way to do it is to put the static version in the package declaration and use importlib inside the module.
The text was updated successfully, but these errors were encountered: