-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
ResolutionImpossible
error message does not distinguish between extras
#10873
Comments
Sometimes, pip provides the different output: The conflict is caused by:
resolution-impossible-with-extras[extra1,extra2,extra3] 0.0.0 depends on pandas<2 and >=1.3
resolution-impossible-with-extras[extra1,extra2,extra3] 0.0.0 depends on pandas==1.4.0
resolution-impossible-with-extras[extra1,extra2,extra3] 0.0.0 depends on pandas==1.4.1 Its inconsistent, because |
I haven't managed to get pip to output the message you show here. How did you obtain it? |
Run it several times. |
I also checked pip v21 and it also produced different outputs. |
Seems this different output has been noticed in a couple of other issues #10824 and #10391 (comment) |
If anyone’s interested in improving this, see also #9237. |
FYI the error message does now display the extra being refereed to, if you run on latest Pip you get:
|
Closing as this now appears to be fixed and there was no further feedback. Feel free to open a new issue if there is a new way of reproducing the problem. |
Description
If a package has extras with conflicting dependencies, the error message displayed by pip does not clarify which extras triggered the conflict, and also produces an error message with is rather confusing. Example (see steps to reproduce):
This happens when
extra1
asks forpandas==1.4.0
andextra2
asks forpandas==1.4.1
.extra3
has nothing to do with the conflict, but from the error message it's impossible to tell. In addition, the error message never mentions neither which extras that caused the issue, nor the actual issue, aspandas==1.4.0
is never mentioned.Expected behavior
It should point to the extras that triggered the
ResolutionImpossible
error in a clear way.pip version
22.0.2
Python version
3.9
OS
Ubuntu 21.10
How to Reproduce
Create a
setup.cfg
with the following content:and an "empty"
setup.py
like the following content:Then execute in the same folder:
Output
Code of Conduct
The text was updated successfully, but these errors were encountered: