Nick Coghlan wrote: > New Hierarchy > ============= > > Raisable (formerly Exception) > +-- CriticalException (new) > +-- KeyboardInterrupt > +-- MemoryError > +-- SystemError > +-- ControlFlowException (new) > +-- GeneratorExit > +-- StopIteration > +-- SystemExit > +-- Exception (formerly StandardError)
If CriticalException and ControlFlowException are to be siblings of Exception rather than subclasses of it, they should be renamed so that they don't end with "Exception". Otherwise there will be a confusing mismatch between the actual inheritance hierarchy and the one suggested by the naming. Also, I'm not entirely happy about Exception no longer being at the top, because so far the word "exception" in relation to Python has invariably meant "anything that can be raised". This terminology is even embedded in the syntax with the try-except statement. Changing this could to lead to some awkward circumlocutions in the documentation and confusion in discussions. -- Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | [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
