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 BreamoreBoy, asvetlov, flox, ggenellina, guettli, hoffman, ncoghlan, news1234, pakal, pitrou, r.david.murray, rbcollins, stutzbach, vinay.sajip, vstinner, ysj.ray
Date 2015-03-17.12:28:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1426595334.07.0.888011612035.issue1553375@psf.upfronthosting.co.za>
In-reply-to
Content
Adding Robert Collins to the nosy list to see if the recent traceback changes make it easier to implement this one correctly.

Robert, for context, the general idea here is to be able to stitch the traceback for a caught exception together with the stack trace for the current frame in order to give a full stack trace for the caught exception, rather than just the stack trace up to the frame where it was caught.
History
Date User Action Args
2015-03-17 12:28:54ncoghlansetrecipients: + ncoghlan, vinay.sajip, guettli, hoffman, ggenellina, pitrou, vstinner, rbcollins, stutzbach, pakal, r.david.murray, asvetlov, flox, news1234, ysj.ray, BreamoreBoy
2015-03-17 12:28:54ncoghlansetmessageid: <1426595334.07.0.888011612035.issue1553375@psf.upfronthosting.co.za>
2015-03-17 12:28:54ncoghlanlinkissue1553375 messages
2015-03-17 12:28:53ncoghlancreate