In article <[EMAIL PROTECTED]>, Brett Cannon <[EMAIL PROTECTED]> wrote:
> New Hierarchy > ============= > > Exception > +-- CriticalException (new) > +-- KeyboardInterrupt > +-- MemoryError > +-- SystemError > +-- ControlFlowException (new) > +-- StopIteration > +-- GeneratorExit > +-- SystemExit > +-- StandardError > +-- AssertionError > +-- SyntaxError > +-- IndentationError > +-- TabError > +-- UserException (rename of RuntimeError) > +-- ArithmeticError > +-- FloatingPointError > +-- DivideByZeroError > +-- OverflowError > +-- UnicodeError > +-- UnicodeDecodeError > +-- UnicodeEncodeError > +-- UnicodeTranslateError > +-- LookupError > +-- IndexError > +-- KeyError > +-- TypeError > +-- AttributeError > +-- EnvironmentError > +-- OSError > +-- IOError > +-- EOFError (new inheritance) > +-- ImportError > +-- NotImplementedError (new inheritance) > +-- NamespaceError (rename of NameError) > +-- UnboundGlobalError (new) > +-- UnboundLocalError > +-- UnboundFreeError (new) > +-- WeakReferenceError (rename of ReferenceError) > +-- ValueError > +-- Warning > +-- UserWarning > +-- AnyDeprecationWarning (new) > +-- PendingDeprecationWarning > +-- DeprecationWarning > +-- SyntaxWarning > +-- SemanticsWarning (rename of RuntimeWarning) > +-- FutureWarning I am wondering why OSError and IOError are not under StandardError? This seems a serious misfeature to me (perhaps the posting was just misformatted?). Having one class for "normal" errors (not exceptions whose sole purpose is to halt the program and not so critical that any continuation is hopeless) sure would make it easier to write code that output a traceback and tried to continue. I'd love it. -- Russell _______________________________________________ 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
