On 9/27/07, Greg Ewing [EMAIL PROTECTED] wrote:
Gregory P. Smith wrote:
Is IOError is the right name to use? OSError is raised for things that
are not IO such as subprocess, dlopen, system.
The trouble with either of these is that the class
of errors we're talking about don't necessarily
Greg Ewing writes:
Gregory P. Smith wrote:
Is IOError is the right name to use? OSError is raised for things that
are not IO such as subprocess, dlopen, system.
The trouble with either of these is that the class
of errors we're talking about don't necessarily come
directly from
On 9/28/07, Stephen J. Turnbull [EMAIL PROTECTED] wrote:
Greg Ewing writes:
Gregory P. Smith wrote:
Is IOError is the right name to use? OSError is raised for things that
are not IO such as subprocess, dlopen, system.
The trouble with either of these is that the class
of
On 9/28/07, Guido van Rossum [EMAIL PROTECTED] wrote:
On 9/28/07, Stephen J. Turnbull [EMAIL PROTECTED] wrote:
Greg Ewing writes:
Gregory P. Smith wrote:
Is IOError is the right name to use? OSError is raised for things that
are not IO such as subprocess, dlopen, system.
On 9/28/07, Brett Cannon [EMAIL PROTECTED] wrote:
On 9/28/07, Guido van Rossum [EMAIL PROTECTED] wrote:
On 9/28/07, Stephen J. Turnbull [EMAIL PROTECTED] wrote:
Greg Ewing writes:
Gregory P. Smith wrote:
Is IOError is the right name to use? OSError is raised for things
that
How about making IOError, OSError and EnvironmentError all aliases for
the same thing? The distinction is really worthless historical
baggage.
On 9/26/07, Greg Ewing [EMAIL PROTECTED] wrote:
Jim Jewett wrote:
In particular, should socket.error, ftp.Error and
httplib.HTTPException (used in
On 9/27/07, Guido van Rossum [EMAIL PROTECTED] wrote:
How about making IOError, OSError and EnvironmentError all aliases for
the same thing? The distinction is really worthless historical
baggage.
+1 on that.
___
Python-Dev mailing list
On 9/27/07, Guido van Rossum [EMAIL PROTECTED] wrote:
How about making IOError, OSError and EnvironmentError all aliases for
the same thing? The distinction is really worthless historical
baggage.
+1 from me.
Should OSError and IOError become aliases to EnvironmentError? I
assume
On 27 Sep 2007, 21:23:58, Brett Cannon wrote:
Should OSError and IOError become aliases to EnvironmentError? I
assume WindowsError and VMSError will just directly subclass which
ever exception sticks around.
And should we bother with a PendingDeprecationWarning for IOError or
OSError? Or
I'd be happy to make them all IOError. 2to3 can clean this up.
On 9/27/07, Graham Horler [EMAIL PROTECTED] wrote:
On 27 Sep 2007, 21:23:58, Brett Cannon wrote:
Should OSError and IOError become aliases to EnvironmentError? I
assume WindowsError and VMSError will just directly subclass which
On 9/27/07, Guido van Rossum [EMAIL PROTECTED] wrote:
How about making IOError, OSError and EnvironmentError all aliases for
the same thing? The distinction is really worthless historical
baggage.
Wouldn't it also be nice to have some subclasses of IOError like
FileNotFoundError,
I suspect that the use case for those errors is far less than you think.
On 9/27/07, BJörn Lindqvist [EMAIL PROTECTED] wrote:
On 9/27/07, Guido van Rossum [EMAIL PROTECTED] wrote:
How about making IOError, OSError and EnvironmentError all aliases for
the same thing? The distinction is really
Guido van Rossum wrote:
How about making IOError, OSError and EnvironmentError all aliases for
the same thing? The distinction is really worthless historical
baggage.
To my mind, the distinction is that IOError and OSError
have an attribute for the error code, and the code found
there has a
Is IOError is the right name to use? OSError is raised for things that are
not IO such as subprocess, dlopen, system.
Nobody likes typing out EnvironmentError and dislike the suggestion of
EMError, should it just be OSError? errno values are after all OS specific.
-gps
On 9/27/07, Guido van
Gregory P. Smith wrote:
Is IOError is the right name to use? OSError is raised for things that
are not IO such as subprocess, dlopen, system.
The trouble with either of these is that the class
of errors we're talking about don't necessarily come
directly from the OS or I/O library.
Often I
urllib goes to goes to some trouble to ensure that it raises IOError,
even when the underlying exception comes from another module.[*] I'm
wondering if it would make sense to just have those modules'
exceptions inherit from IOError.
In particular, should socket.error, ftp.Error and
Shouldn't these all inherit from EnvironmentError?
Or should EnvironmentError and IOError be the same thing perhaps?
--Guido
On 9/26/07, Jim Jewett [EMAIL PROTECTED] wrote:
urllib goes to goes to some trouble to ensure that it raises IOError,
even when the underlying exception comes from
Jim Jewett wrote:
In particular, should socket.error, ftp.Error and
httplib.HTTPException (used in Py3K) inherit from IOError?
I'd say that if they incorporate a C library result code they
should inherit from IOError, or if they incorporate a system
call result code they should inherit from
18 matches
Mail list logo
