You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2021-12-06.23:31:14.461>created_at=<Date2015-11-16.08:42:51.704>labels= ['type-bug', 'docs']
title='The documentation for urllib.request should mention http.client.HTTPException'updated_at=<Date2021-12-06.23:31:14.460>user='https://bugs.python.org/jonorebro'
The documentation for urllib.request should mention that a robust client using urllib.request must be prepared for exceptions of type http.client.HTTPException in addition to urllib.error.URLError.
Example: the server breaks HTTP and returns an empty status line and we get a http.client.BadStatusLine.
Closely related: bpo-22797 proposes documenting some circumstances where ValueError is raised directly. Perhaps you can review and enhance the patch already there.
Also related:
bpo-13736 proposes to wrap http.client exceptions (which I disagree with), and add extra wrapping for socket.error (which I may agree with for consistency), and document existing “exception leaks”.
bpo-6471 discusses awkwardnesses of getting at the underlying exception that URLError wraps.
bpo-22797 was resolved by being more specific about when a URLError is raised, rather than mentioning other exceptions as well. Do we want to do more than that, or can this be closed as well?
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: