-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Comments
Related #993 |
Any other feedback on this? Could this just be made a warning, and the first / existing dep/requirement would be used?! |
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. |
👍 need this |
Unless all of these references are top level which is the case here :) |
I'm closing this, the fundamental issue here is #988 and this will effectively be solved by solving that issue. |
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):
This results in the following error:
The text was updated successfully, but these errors were encountered: