➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients adaptivelogic, eric.snow, gvanrossum, martius, ncoghlan, pitrou, rbcollins, rhettinger, vstinner, yselivanov
Date 2015-02-05.10:49:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1423133367.11.0.381711403903.issue17911@psf.upfronthosting.co.za>
In-reply-to
Content 
+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?
History
Date User Action Args
2015-02-05 10:49:27ncoghlansetrecipients: + ncoghlan, gvanrossum, rhettinger, pitrou, vstinner, rbcollins, eric.snow, yselivanov, adaptivelogic, martius
2015-02-05 10:49:27ncoghlansetmessageid: <1423133367.11.0.381711403903.issue17911@psf.upfronthosting.co.za>
2015-02-05 10:49:27ncoghlanlinkissue17911 messages
2015-02-05 10:49:26ncoghlancreate