[Python-Dev] IO module precisions and exception hierarchy (original) (raw)
James Y Knight foom at fuhm.net
Sun Sep 27 17:43:00 CEST 2009
- Previous message: [Python-Dev] IO module precisions and exception hierarchy
- Next message: [Python-Dev] PEP 389: argparse - new command line parsing module
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sep 27, 2009, at 4:20 AM, Pascal Chambon wrote:
Thus, at the moment IOErrors rather have the semantic of "particular case of OSError", and it's kind of confusing to have them remain in their own separate tree... Furthermore, OSErrors are often used where IOErrors would perfectly fit, eg. in low level I/O functions of the OS module. Since OSErrors and IOErrors are slightly mixed up when we deal with IO operations, maybe the easiest way to make it clearer would be to push to their limits already existing designs.
How about just making IOError = OSError, and introducing your proposed
subclasses? Does the usage of IOError vs OSError have any useful
semantics?
James
- Previous message: [Python-Dev] IO module precisions and exception hierarchy
- Next message: [Python-Dev] PEP 389: argparse - new command line parsing module
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]