Nick Coghlan added the comment: +1 for having the base __init__ API be the exception triple and then a TracebackException.from_exception() class method as an alternate constructor.
However, the redundancy between TracebackException.__init__() and TracebackException.from_exc_tuple() feels very strange to me. It leaves the __init__ working-but-undocumented and isn't a pattern I can recall seeing anywhere else in the standard library. Would it be possible to just add the from_exception() class method and leave the documented (and only) API for building from a triple being the normal constructor call? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17911> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
