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 well-defined meaning (C library error code and system call error code respectively), whereas EnvironmentError is more general. While it might be possible to merge them all together on Unix-like systems, that wouldn't necessarily be true on all platforms -- the IOError and OSError codes might belong to different domains. Although I suppose you could have another attribute to distinguish them if necessary. -- Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | Carpe post meridiem! | Christchurch, New Zealand | (I'm not a morning person.) | [EMAIL PROTECTED] +--------------------------------------+ _______________________________________________ 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
