On 8/10/05, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> > > WindowsError
> > > ------------
> > >
> > > This should be kept.  Unlike module specific exceptions, this
> exception
> > > occurs in multiple places and diverse applications.  It is
> appropriate
> > > to list as a builtin.
> > >
> > > "Too O/S specific" is not a reason for eliminating this.  Looking at
> the
> > > codebase there does not appear to be a good substitute.  Eliminating
> > > this one would break code, decrease clarity, and cause modules to
> grow
> > > competing variants.
> 
> [Brett]
> > I unfortunately forgot to add that the exception would be moved under
> > os, so it would be more of a renaming than a removal.
> 
> Isn't OSError already used for another purpose (non-platform dependent
> exceptions raised by the os module)?
> 

Don't quite follow what that has to do with making WindowsError become
os.WindowsError.  Yes, OSError is meant for platform-agnostic OS
errors by the os module, but how does that affect the proposed move of
WindowsError?

-Brett
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to