version 20.2 doesn't like non numeric requirements

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.

---

• Bitbucket: https://bitbucket.org/pypa/setuptools/issue/499

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):

---

I think the issue is that the bump to Packaging 16 has made the version parsing more strict. According to the PEP 440, those local version specifies should be 0.1.2+xy1.

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):

---

Add test capturing previously allowed usage. Ref #499.

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):

---

@stevenk_: Can you review this issue? Was this an intentional limitation? How difficult would it be to restore the prior expectation, captured by the above test?

Original comment by lukasgraf (Bitbucket: lukasgraf, GitHub: lukasgraf):

---

Has 20.2 since been pulled from PyPi, or am I imagining things?

Original comment by jaraco (Bitbucket: jaraco, GitHub: jaraco):

---

Yes, that's right. Until we can triage the issue and determine a plan forward, I want to avoid causing harm to existing deployments.

Original comment by lukasgraf (Bitbucket: lukasgraf, GitHub: lukasgraf):

---

I see, thank you for clarifying.

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 jaraco (Bitbucket: jaraco, GitHub: jaraco):

---

Update to packaging 16.4. Fixes #499.

Original comment by lukasgraf (Bitbucket: lukasgraf, GitHub: lukasgraf):

---

With setuptools-20.2.1 I'm seeing another regression. Parsing the requirement plone.app.portlets >=2.5.1, <3.0(which used to work before 20.2) now fails with InvalidRequirement: Invalid requirement, parse error at "'<3.0'".

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 passlib >= 1.6, < 2.0. When I run the install using setuptools 20.1, everything works, but with 20.2.1, it doesn't and fails with "error in SQLAlchemy-Utils setup command: 'extras_require' must be a dictionary whose values are strings or lists of strings containing valid project/version requirement specifiers.".

When I remove the passlib requirement, it installs just fine.