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 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 <>
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):

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.
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: <>
2017-06-06 04:00:58ncoghlanlinkissue30579 messages
2017-06-06 04:00:58ncoghlancreate