From dd6c4adb2e3a4dd2d99b9854d41ae9d3ce783cfb Mon Sep 17 00:00:00 2001 From: Dos Moonen Date: Sat, 28 Dec 2024 18:38:40 +0100 Subject: [PATCH] Remove section about non-existing `--force-keyring` flag (#12455) I must have messed up while merging/rebasing at some point... --- docs/html/topics/authentication.md | 19 ------------------- news/12455.doc.rst | 1 + 2 files changed, 1 insertion(+), 19 deletions(-) create mode 100644 news/12455.doc.rst diff --git a/docs/html/topics/authentication.md b/docs/html/topics/authentication.md index a2649071762..076a9269f5c 100644 --- a/docs/html/topics/authentication.md +++ b/docs/html/topics/authentication.md @@ -163,25 +163,6 @@ from the subprocess in which they run Pip. You won't know whether the keyring backend is waiting the user input or not in such situations. ``` -pip is conservative and does not query keyring at all when `--no-input` is used -because the keyring might require user interaction such as prompting the user -on the console. You can force keyring usage by passing `--force-keyring` or one -of the following: - -```bash -# possibly with --user, --global or --site -$ pip config set global.force-keyring true -# or -$ export PIP_FORCE_KEYRING=1 -``` - -```{warning} -Be careful when doing this since it could cause tools such as pipx and Pipenv -to appear to hang. They show their own progress indicator while hiding output -from the subprocess in which they run Pip. You won't know whether the keyring -backend is waiting the user input or not in such situations. -``` - Note that `keyring` (the Python package) needs to be installed separately from pip. This can create a bootstrapping issue if you need the credentials stored in the keyring to download and install keyring. diff --git a/news/12455.doc.rst b/news/12455.doc.rst new file mode 100644 index 00000000000..2e0d4c1970c --- /dev/null +++ b/news/12455.doc.rst @@ -0,0 +1 @@ +Removed section about non-existing ``--force-keyring`` flag.