-
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
request for backtracking output to say what the multiple dependencies causing conflicts are #9254
Comments
Craig provided sample output:
It sounds like @craigcalef would like the line "pip is looking at multiple versions of REDACTEDPACKAGE to determine which version is compatible with other requirements." to more specifically say what it's conflicting with. |
A small comment here from testing #9203 I ran pip in verbose mode vs. non-verbose mode and it didn't seem to make a difference, here is a very small sample of the output I get:
So I can see it's looking at setuptools 51.0.0, and I can see there is some conraint on But the logs don't tell me why it's repeating this line repeatedly:
Is there a specific requirement it's testing against? Is it checking different versions of the above multiple packages? And what exactly is the problem as it says "Requirment alread satisfied", surely that's a good thing? It's hard to know how to improve the contraints when I don't know what pip is getting tripped up on exactly. |
That log line is omitted repeated only due to a quirk in pip’s existing code structure (that has nothing to do with the resolver), and does not mean anything particularly useful, unfortunately. |
Hey folks -- created #9258 to potentially help address this, as I ran into something similar. Not sure if the user on Twitter ran into the same thing as me, but I found using the new resolver has led to a lot of hard-to-debug issues since it only pprints out the versioning conflicts once it finally gives up on backtracking. I added a new flag for selectively disabling that, which makes it much easier to get the conflict info immediately and fix it, especially for cases which are 100% incompatible but have a large amount of cases which need to be tried before the resolver realizes that. |
Fixes pypagh-9254. Closes pypagh-10258. See pypa#10258 (comment) for inspiration.
Pursuing a simpler approach to fix this issue at #10937. I think the output now is much more informative. Folks are welcome to try it out and see if it helps debugging backtracking situations. |
Fixes pypagh-9254. Closes pypagh-10258. See pypa#10258 (comment) for inspiration.
Fixes pypagh-9254. Closes pypagh-10258. See pypa#10258 (comment) for inspiration.
I was conversing with @craigcalef (I believe) on Twitter who said:
and
Craig, could you share a bit of sample output with us so we can look at it concretely and decide what to insert and where? Thanks.
The text was updated successfully, but these errors were encountered: