-
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 update
and poetry lock
switch versions back and forth
#4243
Comments
Apparently this is caused because there are two right ways to resolve dependencies here:
So either requests==2.15.1 and idna==3.2 or requests==2.25.1 and idna==2.10 satisfies the constraints. Either way, Poetry should probably choose one and stick to it, although I'm not sure what's the best way to choose the "right" pins in this case. |
FYI, requests 2.26.0 was released which allows idna 3.x, so you will have to pin requests to |
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
I have a
pyproject.toml
file with"discord.py" = "^1.7.3"
anddemoji = "^0.4.0"
, then runpoetry install
to install dependencies and generate an initial lock file.If I run
poetry lock
afterwards, nothing happens, as the lock file is up to date.Now, if I run
poetry update
, it updatesrequests
from 2.15.1 to 2.25.1, and downgradesidna
from 3.2 to 2.10 (in the lock file as well).However, if I run
poetry lock
again after, it reverts the changes thatpoetry update
made to the lock file. I can keep repeating this back and forth and end up with two inconsistent lock files.The text was updated successfully, but these errors were encountered: