[Python-ideas] PEP 3151: Reworking the OS and IO exception hierarchy

M.-A. Lemburg mal at egenix.com
Wed Jul 28 15:06:44 CEST 2010

Antoine Pitrou wrote:
> Hello,
> On Sat, 24 Jul 2010 14:31:42 -0700
> "Gregory P. Smith" <greg at krypto.org> wrote:
>> The EnvrionmentError hierarchy and common errno test code has bothered me
>> for a while.  While I think the namespace pollution concern is valid I would
>> suggest adding "Error" to the end of all of the names (your initial proposal
>> only says "Error" on the end of one of them) as that is consistent with the
>> bulk of the existing standard exceptions and warnings.  They are unlikely to
>> conflict with anything other than exceptions people have already defined
>> themselves in any existing code (which could likely be refactored out after
>> we officially define these).
> The reason I haven't added "Error" to them is that the names are
> already quite long, and it's quite obvious that they refer to errors.
> I'm obviously not religious about it, though :)

Please keep the "Error" suffix on those exception class names. This is
common practice and we wouldn't want to break with it just because
the names get a little longer (we have editor type completion to
deal with that ;-).

Marc-Andre Lemburg

Professional Python Services directly from the Source  (#1, Jul 28 2010)
>>> Python/Zope Consulting and Support ...        http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ...             http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ...        http://python.egenix.com/

::: Try our new mxODBC.Connect Python Database Interface for free ! ::::

   eGenix.com Software, Skills and Services GmbH  Pastor-Loeh-Str.48
    D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
           Registered at Amtsgericht Duesseldorf: HRB 46611

More information about the Python-ideas mailing list