-
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 self update warning: The locked version 1.5.0 for shellingham is a yanked version. #7344
Comments
I'm not sure this is a bug or there's anything that makes sense to do here; if you reinstall Poetry this should solve itself. The release became yanked between the time you installed Poetry and the time you attempted to self-update, and Poetry will not opt out of a yanked version when already selected. It's possible to manually massage this, but if you are concerned, reinstalling is a better/easier way to handle this. |
A reinstall gets me a different set of dependencies than an update? This sounds like I get a different poetry every time I install it. This is … terrifying! |
Yes, Poetry is installed as a normal Python package and the version constraints we set in pyproject.toml are exported. |
Reinstall (without an intervening uninstall) didn't help. % curl -sSL https://install.python-poetry.org | python3 -
Retrieving Poetry metadata
# Welcome to Poetry!
This will download and install the latest version of Poetry,
a dependency and package manager for Python.
It will add the `poetry` command to Poetry's bin directory, located at:
/Users/bruce/.local/bin
You can uninstall at any time by executing this script with the --uninstall option,
and these changes will be reverted.
Installing Poetry (1.3.2): Done
Poetry (1.3.2) is installed now. Great!
You can test that everything is set up by executing:
`poetry --version`
% poetry --version
Poetry (version 1.3.2)
% poetry self update
Updating Poetry version ...
Using version ^1.3.2 for poetry
Updating dependencies
Resolving dependencies... (0.4s)
Warning: The locked version 1.5.0 for shellingham is a yanked version. Reason for being yanked: Incorrect package metadata
Writing lock file
Package operations: 1 install, 20 updates, 0 removals
• Updating certifi (2022.12.7 -> 2022.6.15)
• Updating charset-normalizer (3.0.1 -> 2.1.1)
• Updating idna (3.4 -> 3.3)
• Updating urllib3 (1.26.14 -> 1.26.12)
• Updating attrs (22.2.0 -> 22.1.0)
• Updating filelock (3.9.0 -> 3.8.0)
• Updating platformdirs (2.6.2 -> 2.5.2)
• Installing pyparsing (3.0.9)
• Updating pyrsistent (0.19.3 -> 0.18.1)
• Updating rapidfuzz (2.13.7 -> 2.13.4)
• Updating requests (2.28.2 -> 2.28.1)
• Updating dulwich (0.20.50 -> 0.20.46)
• Updating jsonschema (4.17.3 -> 4.15.0)
• Updating keyring (23.13.1 -> 23.11.0)
• Updating packaging (23.0 -> 21.3)
• Updating pkginfo (1.9.6 -> 1.8.3)
• Updating requests-toolbelt (0.10.1 -> 0.9.1)
• Updating shellingham (1.5.0.post1 -> 1.5.0)
• Updating tomlkit (0.11.6 -> 0.11.4)
• Updating trove-classifiers (2023.1.12 -> 2022.12.1)
• Updating virtualenv (20.17.1 -> 20.16.4)
Warning: The file chosen for install of shellingham 1.5.0 (shellingham-1.5.0-py2.py3-none-any.whl) is yanked. Reason for being yanked: Incorrect package metadata Same behavior with an uninstall. % curl -sSL https://install.python-poetry.org | python3 - --uninstall
Removing Poetry (1.3.2)
% curl -sSL https://install.python-poetry.org | python3 -
Retrieving Poetry metadata
# Welcome to Poetry!
This will download and install the latest version of Poetry,
a dependency and package manager for Python.
It will add the `poetry` command to Poetry's bin directory, located at:
/Users/bruce/.local/bin
You can uninstall at any time by executing this script with the --uninstall option,
and these changes will be reverted.
Installing Poetry (1.3.2): Done
Poetry (1.3.2) is installed now. Great!
You can test that everything is set up by executing:
`poetry --version`
% poetry self update
Updating Poetry version ...
Using version ^1.3.2 for poetry
Updating dependencies
Resolving dependencies... (0.2s)
Warning: The locked version 1.5.0 for shellingham is a yanked version. Reason for being yanked: Incorrect package metadata
Writing lock file
Package operations: 1 install, 21 updates, 0 removals
• Updating certifi (2022.12.7 -> 2022.6.15)
• Updating charset-normalizer (3.0.1 -> 2.1.1)
• Updating idna (3.4 -> 3.3)
• Updating urllib3 (1.26.14 -> 1.26.12)
• Updating attrs (22.2.0 -> 22.1.0)
• Updating filelock (3.9.0 -> 3.8.0)
• Updating importlib-metadata (6.0.0 -> 4.13.0)
• Updating platformdirs (2.6.2 -> 2.5.2)
• Installing pyparsing (3.0.9)
• Updating pyrsistent (0.19.3 -> 0.18.1)
• Updating rapidfuzz (2.13.7 -> 2.13.4)
• Updating requests (2.28.2 -> 2.28.1)
• Updating dulwich (0.20.50 -> 0.20.46)
• Updating jsonschema (4.17.3 -> 4.15.0)
• Updating keyring (23.13.1 -> 23.11.0)
• Updating packaging (23.0 -> 21.3)
• Updating pkginfo (1.9.6 -> 1.8.3)
• Updating requests-toolbelt (0.10.1 -> 0.9.1)
• Updating shellingham (1.5.0.post1 -> 1.5.0)
• Updating tomlkit (0.11.6 -> 0.11.4)
• Updating trove-classifiers (2023.1.12 -> 2022.12.1)
• Updating virtualenv (20.17.1 -> 20.16.4)
Warning: The file chosen for install of shellingham 1.5.0 (shellingham-1.5.0-py2.py3-none-any.whl) is yanked. Reason for being yanked: Incorrect package metadata This continues to feel like a bug to me. (I won't claim it is a terribly important bug, but it feels like a bug.) |
Okay, right, a uninstall won't remove the lock file. So I think this relates more to how we handle the internal lock file (seen here, because it was preserved, you downgraded to match your previous Poetry install). |
Interesting. OK. Took me a moment to find the lock file. Deleting it and reinstalling poetry got me to a better place. Thanks! |
Same here:
Results:
|
I confirm this. It was the only way I found to restore my poetry install. |
Also have these error. Tried to remove it from poetry. But i don't know how to do that. And python don't know that module. |
You can |
These helped! |
The To update the dependencies one can do:
|
Hi all, I am getting the same bug however I am not able to find the file pypoetry/poetry.lock I tried installing and reinstalling poetry and I still get the bug and I can't find the pypoetry/poetry.lock How can I find the lock file? |
Did you try:
|
As a note I hit this when upgrading from 1.3.2 to 1.4.1, so in this case I was upgrading to a new Poetry release but still see the yanked warning. I personally feel like Poetry should be treated like an application with its versions pinned so that every user on Poetry version X would get the same exact dependencies. |
I would have the same expectation |
I opened the following issue to propose Poetry ship with locked dependencies to address the root cause of this issue |
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) and have included the output below.Issue
Running
poetry self update
gives the warning message:Rerunning
poetry self update
continues to give the same warning message.Simple run of poetry self update
Debug run of poetry self update
The text was updated successfully, but these errors were encountered: