-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
search does not use proxy on pip 1.3.1 #1017
Labels
auto-locked
Outdated issues that have been locked by automation
C: proxy
Dealing with proxies and networking
C: search
'pip search'
Comments
+1 |
+2 |
+3 |
Any blockers in regards to merging this? |
Observed in pip 1.3.1 on CentOS 6.4 with EPEL's packages. Works:
Doesn't work:
|
This bug also work for pip2 search v. 1.4.1 |
Closing to conglomerate on #1104 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
auto-locked
Outdated issues that have been locked by automation
C: proxy
Dealing with proxies and networking
C: search
'pip search'
Hi all
it seems the issue 207 is still an issue.
While 'pip install' regularly uses the proxy I set (via env var), 'pip search' does not.
Here are the evidences:
strace pip search django
[...]
connect(3, {sa_family=AF_INET, sin_port=htons(80), sin_addr=inet_addr("199.27.76.129")}, 16) = -1 EINPROGRESS (Operation now in progress)
Here it stops for a bunch of seconds trying to reach 199.27.76.129 and then timeouts.
The text was updated successfully, but these errors were encountered: