-
Notifications
You must be signed in to change notification settings - Fork 3.1k
timeout error is noisy #349
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
Labels
auto-locked
Outdated issues that have been locked by automation
C: logging
Information Logging
type: enhancement
Improvements to functionality
Comments
👍 |
mihneadb
added a commit
to mihneadb/pip
that referenced
this issue
Jun 16, 2012
I fixed this issue in my 3rd commit in this pull request [1]. [1] #580 |
<3 |
👍 |
There's also this one:
|
Closing this issue, we've entirely rewritten this part of pip and PyPI has gotten much better to the point that this issue is not being hit enough to warrant fixing it. |
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: logging
Information Logging
type: enhancement
Improvements to functionality
PyPI has apparently been down lately, and my attempts at
pip search
result in unhandled exceptions:the messages are noisy and not very helpful. it would be better if pip caught the exceptions and reported the errors cleanly, identifying which addresses cannot be reached.
The text was updated successfully, but these errors were encountered: