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
version 20.2 doesn't like non numeric requirements #499
Comments
Original comment by stevenk_ (Bitbucket: stevenk_, GitHub: Unknown): No, this was not an intentional limitation. The support for non-PEP 440 specifiers was present, it was just buggy (and untested, sigh). I have corrected both of those issues in pypa/packaging#62, and will submit a PR to update packaging to the new release (expected to be 16.3) when my PR has landed and a packaging release made. |
Original comment by stevenk_ (Bitbucket: stevenk_, GitHub: Unknown): Turns out packaging 16.3 causes another regression, this time with "name (==4)" which is an existing requirement in use in setuptools. I'm trying to sort out the parser so that all cases work. |
Original comment by jaapz (Bitbucket: jaapz, GitHub: jaapz): I am bumping into this issue as well with a dependency I use (SQLAlchemy-Utils), which defines a requirement as When I remove the passlib requirement, it installs just fine. |
Originally reported by: mathiasbc (Bitbucket: mathiasbc, GitHub: mathiasbc)
Latest version 20.2 fails when trying to install requirements in the form:
'mypackage==0.1.2.xy1'
$ python setup.py egg_info
error in mypackage setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers; Invalid requirement, parse error at "'.xy1'"
I was able to confirm that setuptools 20.1 does not present this issue.
The text was updated successfully, but these errors were encountered: