Message235428
| 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? |
|