Skip to content
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

pip does not load credentials from ~/.netrc for the index-url #3569

Closed
ssbarnea opened this issue Mar 15, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@ssbarnea
Copy link
Contributor

commented Mar 15, 2016

pip 8.1.0 from /usr/local/lib/python3.5/site-packages (python 3.5)

I discovered that pip will fail to load credentials from ~/.netrc file for the index-url

Reproduce: configure the index-url = http://hostname inside pip.conf and add netrc credentials to file.
Pip will fail to load them and the alternative is to include the credentials inside the index-url which is a serious issue because these credentials will be logged everywhere.

@ssbarnea

This comment has been minimized.

Copy link
Contributor Author

commented Apr 30, 2016

It seems that pip doesn't do this even with --find-links which prevents us from using private repositories.

ssbarnea added a commit to ssbarnea/pip that referenced this issue Apr 30, 2016

@dstufft

This comment has been minimized.

Copy link
Member

commented May 26, 2016

Fixed by #3715

@dstufft dstufft closed this May 26, 2016

@brettswift

This comment has been minimized.

Copy link

commented Aug 22, 2017

Where is the .netrc file support documented for pip ?

ok, well this post was very helpful. But I came here by way of a few hours of scouring docs trying to get a pip install over HTTPS. I'm newish to python so maybe I just didn't find this in the documentation somewhere.. could someone post the link to the docs for this support of private repos?

I am using pip 9.0.1 and python 3.6.2 and all the searching I went through pointed me at putting a username in a URL...

@lock lock bot added the S: auto-locked label Jun 3, 2019

@lock lock bot locked as resolved and limited conversation to collaborators Jun 3, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.