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 akuchling
Recipients akuchling, ghazel, loewis, pconnell, pitrou, r.david.murray, terry.reedy, tim.peters, vstinner
Date 2013-09-08.15:20:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1378653608.83.0.793181454135.issue1565525@psf.upfronthosting.co.za>
In-reply-to
Content
Here's a patch implementing traceback.clear_tb_frames().  (Feel free to bikeshed about the name.)

One more substantial question: the top frame of the traceback is possibly still running.  Currently the code skips it by doing an initial 'tb = tb.tb_next'.  Would it be better to catch and ignore the RuntimeError 
from frame.clear()?
History
Date User Action Args
2013-09-08 15:20:08akuchlingsetrecipients: + akuchling, tim.peters, loewis, terry.reedy, pitrou, vstinner, ghazel, r.david.murray, pconnell
2013-09-08 15:20:08akuchlingsetmessageid: <1378653608.83.0.793181454135.issue1565525@psf.upfronthosting.co.za>
2013-09-08 15:20:08akuchlinglinkissue1565525 messages
2013-09-08 15:20:08akuchlingcreate