-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Ignore literal duplicates (includes and/or individual requirements) #993
Comments
Just ran into the exact same issue, same use case. |
+1 |
closing as dupe of #56 |
+1 |
I looked at this from the angle of attempting to allow/ignore literal duplicate requirements. One snag was with non-editable url requirements, e.g. pkg urls or vcs urls without e.g. so there could be 2 lines like this
I don't think these 2 should pass thru as literal duplicates, but we don't have enough information stored to distinguish them. we should look into storing the full url I think, and understand why we're not. I'm not sure atm related issue: #1658 |
👍 Pip is more disappointing the more you try to do anything outside of tutorial material. |
+1 same error similiar usecase. |
pip's handling of requirements files does not support a scenario like this one:
Here,
pip install -r development.txt
will complain about a double requirementsomepackage==1.0
and quit.Because of that, I have to duplicate my testing requirements in my development.txt. Not a big deal, but it would be nice if pip could handle this. For this scenario, it seems that it would be sufficient to just ignore the duplicate
-r
line, so this would probably be easier to implement than #56.The text was updated successfully, but these errors were encountered: