Skip to content

Allow to ignore 'Double requirement given' error #2367

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

Closed
blueyed opened this issue Jan 20, 2015 · 6 comments
Closed

Allow to ignore 'Double requirement given' error #2367

blueyed opened this issue Jan 20, 2015 · 6 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@blueyed
Copy link
Contributor

blueyed commented Jan 20, 2015

It would be nice if 'Double requirement given: %s (already in %s, name=%r)' could be made a warning optionally, as long as it does not result in a conflict.

My use case is tox, where 'django' is defined in the test env (with version restrictions), but also in a requirements file (which is meant to install the test env outside of tox):

pip install --pre pytest pytest-django six Django>=1.7,<1.8 -rtest_project/test_requirements.txt

This results in the following error:

Double requirement given: django (from -r test_project/requirements.txt (line 3)) (already in Django<1.8,>=1.7, name='django')

@piotr-dobrogost
Copy link

Related #993

@blueyed
Copy link
Contributor Author

blueyed commented Feb 24, 2015

Any other feedback on this?

Could this just be made a warning, and the first / existing dep/requirement would be used?!

@rbtcollins
Copy link

So the underlying issue here is #988 - without that we can't handle the interactions that occur dealing with multiply encountered references to the same distribution.

@c0b
Copy link

c0b commented Jul 15, 2016

👍 need this

@piotr-dobrogost
Copy link

@rbtcollins

So the underlying issue here is #988 - without that we can't handle the interactions that occur dealing with multiply encountered references to the same distribution.

Unless all of these references are top level which is the case here :)

@dstufft
Copy link
Member

dstufft commented Mar 30, 2017

I'm closing this, the fundamental issue here is #988 and this will effectively be solved by solving that issue.

@dstufft dstufft closed this as completed Mar 30, 2017
@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 3, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

No branches or pull requests

5 participants