You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Poetry takes very much time to lock on a specific set of dependencies #2137
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.
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.
with python = "^3.6" this pyproject.toml solves more or less immediately
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 awscli, or using more recent Python versions), going to close this issue, because there's not that much things that Poetry can do given how the resolver works.
Activity
dimbleby commentedon Apr 18, 2022
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.
with
python = "^3.6"this pyproject.toml solves more or less immediatelysticking with python 3.5 but adding extra constraints to help poetry never choose packages that require python >=3.6 is less effective than I had hoped - but in combination with Ignore combinations of overrides whose intersection of markers is empty #4695 it does solve quickly
mkniewallner commentedon Jul 10, 2022
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
awscli, or using more recent Python versions), going to close this issue, because there's not that much things that Poetry can do given how the resolver works.mm-matthias commentedon Jul 12, 2022
Probably a duplicate of #5896 .
github-actions commentedon Mar 1, 2024
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.