Changes by Armin Rigo [EMAIL PROTECTED]:
--
nosy: -arigo
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1481036
_
___
Python-bugs-list mailing list
Armin Rigo [EMAIL PROTECTED] added the comment:
This will break many existing applications, no? I can easily think of
examples of reasonable code that would no longer work as intended.
What's even worse, breakage might only show up in exceptional cases and
give obscure results (e.g. reporting
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Py3k then?
--
versions: +Python 3.0 -Python 2.6
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1481036
_
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Something like this was done in 2.5.
--
nosy: +benjamin.peterson
resolution: - fixed
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1481036
_
Changes by Benjamin Peterson [EMAIL PROTECTED]:
--
status: open - closed
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1481036
_
___
Python-bugs-list mailing
Gregory P. Smith [EMAIL PROTECTED] added the comment:
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,
Changes by Gregory P. Smith [EMAIL PROTECTED]:
--
resolution: fixed -
status: closed - open
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1481036
_
___
Benjamin Peterson [EMAIL PROTECTED] added the comment:
Yes, that'd make sense. Ask on python-dev, though.
--
resolution: - fixed
status: open - closed
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1481036
Gregory P. Smith [EMAIL PROTECTED] added the comment:
The problem with EOFError as a child of EnvironmentError is that it
wouldn't conform to EnvironmentError's standard 2-tuple or 3-tuple of
args representing errno and the associate string and optionally filename.
So inserting an exception
