Author ncoghlan
Recipients brett.cannon, eric.snow, giampaolo.rodola, ncoghlan, njs, vstinner, yselivanov
Date 2017-06-06.04:00:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1496721658.99.0.708916843635.issue30579@psf.upfronthosting.co.za>
In-reply-to
Content
Rather than allowing this on tracebacks directly, I'd prefer to build on the "TracebackException" work and allow traceback summaries in all the places where we currently require real tracebacks (including exception __traceback__ attributes): https://docs.python.org/3/library/traceback.html#tracebackexception-objects

The essential requirement here would be to abstract out a "traceback protocol" from the current concrete traceback objects, and adapt affected parts of the interpreter (such as the traceback display on shutdown) to use that abstract protocol when dealing with a non-native traceback object.
History
Date User Action Args
2017-06-06 04:00:59ncoghlansetrecipients: + ncoghlan, brett.cannon, vstinner, giampaolo.rodola, njs, eric.snow, yselivanov
2017-06-06 04:00:58ncoghlansetmessageid: <1496721658.99.0.708916843635.issue30579@psf.upfronthosting.co.za>
2017-06-06 04:00:58ncoghlanlinkissue30579 messages
2017-06-06 04:00:58ncoghlancreate