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 njs
Recipients brett.cannon, eric.snow, giampaolo.rodola, ncoghlan, njs, vstinner, yselivanov
Date 2017-06-06.04:24:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
My understanding is that the major difference between a real traceback object and a TracebackException object is that the latter is specialized for printing, so it can be lighter weight (no pinning of frame objects in memory), but loses some utility (can't do post-mortem debugging).

If that's right, then that's definitely not a solution, because trio and jinja2 and import errors all need to support post-mortem debugging.

I'm not against the idea of defining a traceback protocol, but it seems like a lot of work when the existing traceback objects are already perfectly good container objects that are just missing a few simple features.
Date User Action Args
2017-06-06 04:24:23njssetrecipients: + njs, brett.cannon, ncoghlan, vstinner, giampaolo.rodola, eric.snow, yselivanov
2017-06-06 04:24:23njssetmessageid: <>
2017-06-06 04:24:23njslinkissue30579 messages
2017-06-06 04:24:23njscreate