-
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
New Resolver: Do not attempt to use an sdist for the same version after a wheel does not match #8129
Comments
Source: #7406 (comment) @pfmoore @uranusjr I think this is a really good test case for us to manually check how "done" we are. @ei8fdb This is a pretty good test case, for using in user testing and research, during beta phase of the new resolver. This is a situation where the resolver would do a lot of things, and it needs to communicate to the user what it is doing. There's a lot of download, choices being made about dependencies, backtracking choices made and so on going on here. |
I think I know why this is happening (we’re returning multiple candidates of the same version from |
Interesting case, and I agree with @uranusjr's diagnosis. A fix for this will conflict with the upgrade strategy changes. That's not a big deal, but I'd mildly prefer to leave this until after 20.1 final so that we can co-ordinate the two changes. Unless I'm misreading the context, I don't think this is newly identified by the beta, so there's no immediate reason to suggest it should be pushed into 20.1. |
Yea, I thought so too.
No hurries from my end. :) |
Oh, and since I haven't mentioned it here -- we're hitting |
Had we fixed this yet? |
We did! I tried this earlier today. :) |
Environment
Description
pip attempts to download and build an sdist for a package during resolution, when a wheel is not compatible.
Expected behavior
How to Reproduce
pip install pyrax==1.9.8 --unstable-feature=resolver
Output
The text was updated successfully, but these errors were encountered: