-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Improve network error message #8641
Comments
Also including #6085 to this one, since they can be solved in a similar way, only the exception we want to catch is different.
This happens when the user has a proxy configuration problem. |
I took a look at the implementation, and it seems like there’s no easy way to change the ugly I think the best we can do here is to output something more useful to the user when pip hits the max retry count. |
Check the following:
Maybe there are some possible reasons for the error message. |
What's the problem this feature will solve?
pip automatically retries after hitting a network error, but the warning it emits is cryptic to users without experience on networking applications.
Recent examples: #7424 #8639.
The typical message a user gets would be something like:
This is not too difficult to discern the error message as a client side networking issue with some Python and network experience. Less experienced users, however, cannot understand what to do to the cryptic output, and end up posting issues.
Describe the solution you'd like
Following the recent effort to format more user-friendly error messages, output a more descriptive message that says
Additional context
I have not thought deep into how this should be implemented, to be honest. We should probably do two things:
Retry(...)
andConnectTimeoutError(...)
objects’ appearances (__repr__
?) in it.The text was updated successfully, but these errors were encountered: