pkg_resources._vendor.packaging.requirements.InvalidRequirement: Invalid requirement, parse error at "'and plat'"

[ghost]

Originally reported by: Anonymous

---

../ve/bin/python setup.py --quiet develop
Traceback (most recent call last):
File "setup.py", line 92, in
setup(**config)
File "/usr/lib64/python2.7/distutils/core.py", line 152, in setup
dist.run_commands()
File "/usr/lib64/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
File "/usr/lib64/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
File "build/bdist.linux-x86_64/egg/setuptools/command/develop.py", line 34, in run
File "build/bdist.linux-x86_64/egg/setuptools/command/develop.py", line 133, in install_for_development
File "build/bdist.linux-x86_64/egg/setuptools/command/easy_install.py", line 720, in process_distribution

File "build/bdist.linux-x86_64/egg/pkg_resources/init.py", line 838, in resolve
File "build/bdist.linux-x86_64/egg/pkg_resources/init.py", line 2462, in requires
File "build/bdist.linux-x86_64/egg/pkg_resources/init.py", line 2686, in _dep_map
File "build/bdist.linux-x86_64/egg/pkg_resources/init.py", line 2696, in _compute_dependencies
File "build/bdist.linux-x86_64/egg/pkg_resources/_vendor/packaging/requirements.py", line 94, in init
pkg_resources._vendor.packaging.requirements.InvalidRequirement: Invalid requirement, parse error at "'and plat'"

Version 20.1 works fine, 20.2 breaks.

---

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

[ghost]

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

---

+1 got the same with latest setuptools and python2.6

pkg_resources._vendor.packaging.requirements.InvalidRequirement: Invalid requirement, parse error at "'and plat'"

[ghost]

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

---

Duplicate of #502.

[ghost]

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

---

Issue #509 was marked as a duplicate of this issue.

[ghost]

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

---

Issue #512 was marked as a duplicate of this issue.

[ghost]

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

---

Issue #518 was marked as a duplicate of this issue.

[ghost]

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

---

(Might be) related IPython issue

ipython/ipython#9311

[ghost]

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

---

It's not; I'm seeing the same thing with no IPython involved.

[ghost]

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

---

i had this issue due to having old version of futures installed. once i deleted it(2.2.0) and reinstalled latest version(3.0.5) the issue has been resolved

[ghost]

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

---

See issue #518 for repro steps that are also using an older version of futures

[ghost]

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

---

Setuptools broke backwards compatibility in 20.2 by delegating requirements to packaging, which in itself is a good thing but packaging does not support the obsolete python_implementation marker which futures 2.2 uses. If this is to be fixed, packaging needs to restore backwards compatibility and setuptools must re-vendor the updated packaging then.

[ghost]

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

---

Here's where futures uses that marker.

[ghost]

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

---

I've filed an upstream request to restore that functionality.

[ghost]

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

---

Thank you.