-
Notifications
You must be signed in to change notification settings - Fork 2.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
Resolver appears to run forever #7858
Comments
Amazon for whatever reason publish hundreds and thousands of releases of packages like boto3. If the solver takes an unlucky turn such that it hits a dead end not compatible with any boto3 release, it can take a long time to work through those hundreds and thousands of releases and realise that it is in fact in such a dead end. Provide tighter bounds - then poetry can spot the dead-end more quickly. |
Thanks @dimbleby ! |
I understand the problem here, and the workaround works well enough, but intuitively it seems a bit silly that poetry goes back into the vast abyss of botocore releases looking for an older version of the package to support a newer version of urllib3. If two versions conflict, wouldn't it make more sense to rollback the version of the more recent package? |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Poetry (version 1.4.2)
Python: 3.10.6
Linux Mint 21.1
https://gist.github.com/darkpixel/80c5d24da1d08c75f4a30a131a75a433
I am on the latest stable Poetry version, installed using a recommended method.
I have searched the issues of this repo and believe that this is not a duplicate.
I have consulted the FAQ and blog for any relevant entries or release notes.
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option) and have included the output below.Issue
I tried to upgrade werkzeug, urllib3, botocore, and boto3 and the resolver appears to have hanged.
poetry add werkzeug=^2 urllib3=^2 botocore=^1 boto3=^1
The text was updated successfully, but these errors were encountered: