New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
develop command should not pin the distribution version precisely #439
Comments
Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco): Can you provide an example replicating this issue? As I try to describe the issue, I realize I'm not even sure under what circumstances the issue occurs. I should think that the version number in the metadata is generated when This leads me to think the issue is only relevant if the user regenerates metadata, such as by running the |
Original comment by RonnyPfannschmidt (Bitbucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt): think of something like using setuptools_scm, do a commit, run tox, then have your local virtualenv break |
Original comment by RonnyPfannschmidt (Bitbucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt): that solution is fabulous, well done |
since setuptools 18.6 fixes the issues with develop installs https://github.com/pypa/setuptools/blob/master/CHANGES.rst#186 pypa/setuptools#439
since setuptools 18.6 fixes the issues with develop installs https://github.com/pypa/setuptools/blob/master/CHANGES.rst#186 pypa/setuptools#439
since setuptools 18.6 fixes the issues with develop installs https://github.com/pypa/setuptools/blob/master/CHANGES.rst#186 pypa/setuptools#439
Originally reported by: RonnyPfannschmidt (Bitbucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt)
When easy_install or pip installs console entry points (scripts), it does so by referencing the installed version of the package. The
develop
command uses the same logic to create executable scripts for a package under development.However, it is common when developing a package that the version number will change, thereafter making the script references invalid (and causing errors when attempting to invoke those scripts).
The text was updated successfully, but these errors were encountered: