Alexander Belopolsky <belopol...@users.sourceforge.net> added the comment:
The proposal is to display builtin subclasses as for example: >>> help(ArithmeticError) class ArithmeticError(Exception) | Base class for arithmetic errors. | | Method resolution order: | ArithmeticError | Exception | BaseException | object | | Built-in subclasses: | FloatingPointError | OverflowError | ZeroDivisionError Note that this really affects only exceptions because no other builtin class has builtin subclasses. (dict has subclasses in collections, but not in builtins.) Exception hierarchy is presented in the reference manual at http://docs.python.org/dev/library/exceptions.html?#exception-hierarchy I wonder if rather than having MRO and subclasses sections, we should just present a portion of the exception hierarchy including the given exception, all its bases and direct subclasses: object | BaseException | Exception | *ArithmeticError* | +-- FloatingPointError +-- OverflowError +-- ZeroDivisionError ---------- title: Small enhancement to help() -> Display exception's subclasses in help() _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8525> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
