Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
docs/changelog.md
Summary of changes
Pass
--no-input
to Pip.Fixes #219
This is a breaking change for keyring users. But was it ever properly supported anyway? As someone who needs the
artifacts-keyring
package to authenticate with our private repo I'm going with the answer beingno, you will have to apply hacks if this is important to you
. Failing fast is better then hanging forever because the user can't see the prompt asking for a username and password.pypa/pip#11698 which is released in Pip 23.1 added a section to the documentation how Pipx users who rely on the keyring library can set things up so keyring will be used again: https://pip.pypa.io/en/stable/topics/authentication/#using-keyring-as-a-command-line-application.
Test plan
It should not have any impact when keyring is not required to authenticate with the repository.
Tested by running the test suite.