Skip to content
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

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

Closed
ghost opened this issue Feb 25, 2016 · 13 comments
Labels

Comments

@ghost
Copy link

@ghost ghost commented Feb 25, 2016

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.


@ghost
Copy link
Author

@ghost ghost commented Feb 25, 2016

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
Copy link
Author

@ghost ghost commented Feb 27, 2016

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


Duplicate of #502.

@ghost
Copy link
Author

@ghost ghost commented Mar 19, 2016

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


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

@ghost
Copy link
Author

@ghost ghost commented Mar 19, 2016

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


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

@ghost
Copy link
Author

@ghost ghost commented Mar 19, 2016

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


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

@ghost
Copy link
Author

@ghost ghost commented Mar 19, 2016

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


(Might be) related IPython issue

ipython/ipython#9311

@ghost
Copy link
Author

@ghost ghost commented Mar 24, 2016

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


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

@ghost
Copy link
Author

@ghost ghost commented Mar 25, 2016

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
Copy link
Author

@ghost ghost commented Mar 25, 2016

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


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

@ghost
Copy link
Author

@ghost ghost commented Mar 26, 2016

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
Copy link
Author

@ghost ghost commented Mar 28, 2016

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


Here's where futures uses that marker.

@ghost
Copy link
Author

@ghost ghost commented Mar 28, 2016

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


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

@ghost
Copy link
Author

@ghost ghost commented Mar 28, 2016

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


Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
0 participants