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 r.david.murray
Recipients akuchling, ghazel, loewis, r.david.murray, terry.reedy, tim.peters, vstinner
Date 2010-06-26.01:51:46
SpamBayes Score 0.002441868
Marked as misclassified No
Message-id <>
Those two references have nothing to do with your request.  They are talking about cycles that get created by grabbing the traceback variable, and the fact that it may take a while before garbage collection reclaims them *after you have let go of the traceback reference*.  You are talking about wanting to release the locals in the stack frame and still hold on to the traceback.  Completely different issue.

Note that while the standard traceback print doesn't reference the locals in the frame, extended tracebacks such as cgitb do.  There is also a proposal to add such locals printing to the standard traceback.

I'm pretty sure this issue isn't going to go anywhere without a patch proposal, but before you work on that you might want to raise the idea on python-ideas and see if a wider audience thinks it is a good idea.
Date User Action Args
2010-06-26 01:51:50r.david.murraysetrecipients: + r.david.murray, tim.peters, loewis, akuchling, terry.reedy, vstinner, ghazel
2010-06-26 01:51:50r.david.murraysetmessageid: <>
2010-06-26 01:51:47r.david.murraylinkissue1565525 messages
2010-06-26 01:51:46r.david.murraycreate