-
Notifications
You must be signed in to change notification settings - Fork 122
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
Build CLI stuck / pip prompt not working with private pypi index #409
Comments
Thanks for reporting, we should be passing |
As expected, this leads the the same issue as if the remote was not known, so:
|
I guess this is related to: pypa/pip#10665 However, from my experience |
For anybody looking for a workaround, set the environment variable |
Nope, that didn't work. How on earth... |
And yet the stack trace and error message don't match at all. |
if I did a pull request that added keyring as a dependency would that be acceptable to the devs? |
Not as a required dep (see #470 and similar discussions, we are keeping required deps to a minimum). |
Hi
We're trying to get a build going with a simple pyproject.toml and setuptools als the build backend.
We have a pip.conf that specifies a private pypi index to be used for all installs.
Running
python -m build
results in the following output being stuck and not moving.Hitting enter twice reveals that the command was blocking the output of the
pip install
invocation in the isolated environment.So pip is asking for user and password using the prompt, but the prompt is hidden.
Which leads to two questions:
Would it be possible to display the prompt normally, so the user can manually enter the credentials to an actual promp? Because entering
myusername<Enter>mypassword<Enter>
seems to work just fine, but one has to figure that out first. Also the user is prompted multiple times, leading to multiple "hidden" prompts.Is there a way to "inject" the pip call somehow to provide the credentials in a non-interactive way?
For example in the CI, we use HTTP basic auth in the form of
pip install -i https://username:[email protected]/simple
.Another way could be to somehow pre-configure keyring to be installed and initialized.
Worst case we could probably use .netrc, but at least for local machines we would like to avoid this (see question 1 regarding multiple prompts.)
On a side note, I'm a bit puzzled that this didn't come up in #246 .
The text was updated successfully, but these errors were encountered: