Message 65420 - Python tracker

➜

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	gregory.p.smith
Recipients	benjamin.peterson, gregory.p.smith, kxroberto
Date	2008-04-12.21:31:56
SpamBayes Score	0.11041335
Marked as misclassified	No
Message-id	<1208035917.79.0.501478395128.issue1481036@psf.upfronthosting.co.za>
In-reply-to

Content
I don't think so. socket.error has been changed to inherit from IOError in 2.6 (and thus socket.sslerror which inherits from socket.error). EOFError has not changed. ftplib.all_errors is already a tuple of (ftplib.Error, socket.error, IOError, EOFError) which demonstrates the issue... Anyways there was discussion on python-dev around the time I made socket.error extend IOError. Adding a new exception to the heirarchy was frowned upon. EnvironmentError is already suitable for that task. Perhaps EOFError should extend EnvironmentError as well?

I don't think so.

socket.error has been changed to inherit from IOError in 2.6 (and thus
socket.sslerror which inherits from socket.error).

EOFError has not changed.

ftplib.all_errors is already a tuple of (ftplib.Error, socket.error,
IOError, EOFError) which demonstrates the issue...

Anyways there was discussion on python-dev around the time I made
socket.error extend IOError.  Adding a new exception to the heirarchy
was frowned upon.  EnvironmentError is already suitable for that task.

Perhaps EOFError should extend EnvironmentError as well?

History
Date	User	Action	Args
2008-04-12 21:31:57	gregory.p.smith	set	spambayes_score: 0.110413 -> 0.11041335 recipients: + gregory.p.smith, kxroberto, benjamin.peterson
2008-04-12 21:31:57	gregory.p.smith	set	spambayes_score: 0.110413 -> 0.110413 messageid: <1208035917.79.0.501478395128.issue1481036@psf.upfronthosting.co.za>
2008-04-12 21:31:56	gregory.p.smith	link	issue1481036 messages
2008-04-12 21:31:56	gregory.p.smith	create