Menu
I've been trying to run pip list -o and pip list --outdated to see if any packages need to be updated but it enters a loop of printing: WARNING: Keyring is skipped due to an exception: Failed to create the collection: Prompt dismissed..
I've upgraded keyring and the version was already up-to-date. I've seen this keyring warning whilst using pip install {package} --upgrade to upgrade other packages as well.
997
Instruct pip to not use a keyring by setting an environment variable (PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring). As far as I know, there is no need to use a keyring for any of the pip commands autospec runs.
If you pip install x and then pip install y, it’s possible that the version of y you get will be different than it would be if you had run pip install x y in a single command.
Providing an editable requirement ( -e .) does not cause pip to ignore version specifiers or constraints (see #8076 ), and if you have a conflict between a pinned requirement and a local directory then pip will indicate that it cannot find a version satisfying both (see #8307)
Sign in to your account jaraco/keyring: v20.0.1 (automatically installed as PIP dependency) Pip block during install, waiting for a keyring to unlock (at least that's my understanding) Pip install should proceed.
I searched the web about that topic and find that GitHub issue.
If your pip version is any version before "21.1", you can try to upgrade pip to the latest version with pip install --upgrade pip command.
Also, as a workaround, you can consider the following answer of jrd from the above link:
Exporting
PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyringprevent python from using any keyring.PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring pipenv updatedoes not ask me anything anymore. So, as a temporary solution, one might want to put this in a .env file.
126
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
