-
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
Poetry takes very much time to lock on a specific set of dependencies #2137
Comments
I don't know whether this was true two years ago, but today it takes poetry a long time to work its way back through awscli versions and find one that's compatible with python 3.5. This is somewhat improved by #5335, but really in such cases the pragmatic thing to do is to put an upper bound on awscli (or use a more recent python) so that poetry doesn't have to check all of the hundreds of later versions.
|
Since Python 3.5 is considered end of life since almost 2 years, and there are actionable solutions to make the resolver faster here (setting a lower bound for |
Probably a duplicate of #5896 . |
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. |
-vvv
option).Issue
While this is not technically a bug, this situation is affecting user experience quite much. With the set of dependencies provided in the linked pyproject file, Poetry takes too long to resolve and generate a lock file. About 1.5 hrs on my machine (quad-core @ 3.7 GHz, so not quite low-end), to be specific.
I have tested this with pip and pipenv, and the latter generates lock in about 17s.
I wonder, if something can be done to improve dependency resolution in such cases, as pipenv test shows that it's totally possible. Though, usually pipenv takes more time to lock & install for me than Poetry.
The text was updated successfully, but these errors were encountered: