On 9/28/07, Stephen J. Turnbull <stephen at xemacs.org> 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 errors we're talking about don't necessarily come > > directly from the OS or I/O library. > > Agree, but I think this is a case where practicality beats purity. > > +1 for OSerror. The OS is a somewhat troublesome abstraction boundary. I/O is a more general concept (and PPBP). +1 for IOError. -- --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4