-
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
2020 resolver stalls during installation #8705
Comments
Apologies, this seems precisely like a duplicate of #8683. I searched for some keywords that don't quite appear in that issue, and neglected to scroll through the first page of issues 🤦 feel free to close—I'll leave open for the moment as a data point. |
For anyone arriving back here—I found that my specific situation was caused by an incompatibility between two I found this while testing whether the solution described here would fix my issue, ultimately finding that I could fix the stalling myself regardless of the resolver version if I just know the right conflicting dependencies to investigate. |
What did you want to do?
We have a private Artifactory registry. The set of dependencies listed in the tree at the end install properly when running the following:
But doing the same with
PIP_USE_FEATURE=2020-resolver
causes a stall. In our CI environment I gave the process as long as 4 hours to complete and it did not.As an experiment I tried installing with the current resolver first and using the 2020 resolver afterward, and was at one point able to see that it was spinning infinitely on
Requirement already satisfied
for some ofpylint
's dependencies. I notice also that the new resolver seems to want to download multiple versions of two different packages thatpylint
depends on (noteastroid
andmccabe
versions in the output below).So far I've been unable to create a more minimal reproduction—attempting to install pylint by itself doesn't cause an issue.
Output
Additional information
pip version: 20.2.1
This example shows the result of running with the new resolver after having run the current resolver already, which provides some evidence that the new resolver seems eager to download more versions:
Dependency tree
The text was updated successfully, but these errors were encountered: