Document how to disable keyring for users who might want to

It’d probably be useful to add something like the following to our documentation. Borrowing from twine:

Disabling Keyring
^^^^^^^^^^^^^^^^^

In some cases, the presence of keyring may be problemmatic. To disable
keyring and defer to a prompt for passwords, uninstall ``keyring``
or if that's not an option, you can also configure keyring to be disabled.

See `twine 338 <https://github.com/pypa/twine/issues/338>`_ for a
discussion on ways to do that.

[hl037]

Wait… IMHO No solution proposed here is likeable ! in my case 👍

1. I want to be able to use pip without having to type a password (to install / uninstall packages etc.) when clearly not necessary
2. I certainly don’t want my keyring password to be blank…
3. I have some modules / app that are using “rightfully” the keyring.

Why is not pip asking for the keyring only when required ? (i.e. when using a private repo, for what this feature has been introduced)… And providing a way to bypass the keyring ?

…This feature will just waste 20 minute or so to many developper either not using keyrings or not understanding why pip behaviour changed…

[skrat]

@SharatChandar I think we should suggest to users to set environment variable PYTHON_KEYRING_BACKEND to keyring.backends.null.Keyring. That disables keyring (the Python package).

We don’t want users disabling the OS keyring password, since that is less secure.

@pradyunsg this is no solution, this will naturally lead users to set that var in their profiles, bashrc, etc. BUT this is affecting behavior of keyring package, not pip. It’s sound to assume that people want to continue using their other python apps depending on keyring. So, really, don’t defer this to keyring’s conf. and come up with a way to configure pip.