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.

Author r.david.murray
Recipients orsenthil, r.david.murray, srid, tarek
Date 2010-05-19.17:03:46
SpamBayes Score 0.000860287
Marked as misclassified No
Message-id <1274288627.63.0.787256134048.issue8721@psf.upfronthosting.co.za>
In-reply-to
Content
Why would you not want to catch all value errors?  I assume (perhaps a bad thing) that distribute will repeat the returned error message in a more user friendly format.  If a bug in urlparse returns a spurious ValueError, that will presumably be found (and then corrected) either by the test suite or by other code in addition to distribute.

The standard library should use standard exceptions unless there is a compelling reason to create a new exception.  This rule of thumb has not always been followed, of course.
History
Date User Action Args
2010-05-19 17:03:47r.david.murraysetrecipients: + r.david.murray, orsenthil, tarek, srid
2010-05-19 17:03:47r.david.murraysetmessageid: <1274288627.63.0.787256134048.issue8721@psf.upfronthosting.co.za>
2010-05-19 17:03:46r.david.murraylinkissue8721 messages
2010-05-19 17:03:46r.david.murraycreate