This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: No documentation for urllib2 exception classes
Type: Stage:
Components: Documentation Versions:
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: fresh, jjlee
Priority: normal Keywords:

Created on 2004-04-29 11:38 by fresh, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg20643 - (view) Author: Chris Withers (fresh) Date: 2004-04-29 11:38
There's not even reference documentation for the
exceptions used by urllib2. 

Documentation of what these are, how you're supposed to
handle them and what attributes you're supposed to play
with would be very handy.

I guess I'll just have to try and glean something from
the source :-S
msg20644 - (view) Author: John J Lee (jjlee) Date: 2005-05-19 20:12
Logged In: YES 
user_id=261020

This is not correct, these exceptions are documented.

(from http://docs.python.org/lib/module-urllib2.html)

The following exceptions are raised as appropriate:

exception URLError
    The handlers raise this exception (or derived
exceptions) when they run into a problem. It is a subclass
of IOError. 

exception HTTPError
    A subclass of URLError, it can also function as a
non-exceptional file-like return value (the same thing that
urlopen() returns). This is useful when handling exotic HTTP
errors, such as requests for authentication. 

exception GopherError
    A subclass of URLError, this is the error raised by the
Gopher handler.
msg20645 - (view) Author: Chris Withers (fresh) Date: 2005-05-20 05:54
Logged In: YES 
user_id=24723

True enough, I guess that some time in the last year this
got updated ;-)
History
Date User Action Args
2022-04-11 14:56:03adminsetgithub: 40199
2004-04-29 11:38:16freshcreate