Author orsenthil
Recipients eric.araujo, ezio.melotti, jmoy, orsenthil, pitrou
Date 2012-02-08.16:26:52
SpamBayes Score 5.63688e-06
Marked as misclassified No
Message-id <1328718412.76.0.292031080962.issue13736@psf.upfronthosting.co.za>
In-reply-to
Content
I have stumbled upon a wrong impression as well by reading the docs, but usually in the code, I tend to catch the specific Exceptions, like timeout instead or URLError when it is known. I saw some libraries following similar pattern too. But that could be changed, if promise in the docs that URLError exception is raised is corrected. 

I think, the course of action for this bug could be.

1. raise ... from .. for the appropriate Exception in 3.3 and appropriate doc changes.
2. Doc changes in 2.7,3.2 which say indicate the possibility of other exceptions besides URLError.

Having any important information in the msg part of the Exception is a bad idea, because it is seldom relied upon and can be changed anytime.

Shall come out with a patch.
History
Date User Action Args
2012-02-08 16:26:52orsenthilsetrecipients: + orsenthil, pitrou, ezio.melotti, eric.araujo, jmoy
2012-02-08 16:26:52orsenthilsetmessageid: <1328718412.76.0.292031080962.issue13736@psf.upfronthosting.co.za>
2012-02-08 16:26:52orsenthillinkissue13736 messages
2012-02-08 16:26:52orsenthilcreate