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 eric.snow, gvanrossum, ncoghlan, pitrou
Date 2013-05-12.04:31:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1368333110.23.0.889135313213.issue17934@psf.upfronthosting.co.za>
In-reply-to
Content
Mostly looks good to me, but I think I'd prefer that attempts to clear a running frame raise RuntimeError with an appropriate message.

I also wonder how this might relate to Eric Snow's proposal to reference the currently executing function from the frame object (see issue 12857). It seems to me that the "f_func" pointer in that patch could serve the same purpose as the "f_executing" boolean flag in this patch, while providing additional information about the execution context.

Some other possibly relevant traceback related resource management issues: issue 6116, issue 1565525, issue 9815 (picked up while searching for Eric's RFE above)

(We may want to add a "clear_frames" convenience method to tracebacks as well)
History
Date User Action Args
2013-05-12 04:31:50ncoghlansetrecipients: + ncoghlan, gvanrossum, pitrou, eric.snow
2013-05-12 04:31:50ncoghlansetmessageid: <1368333110.23.0.889135313213.issue17934@psf.upfronthosting.co.za>
2013-05-12 04:31:50ncoghlanlinkissue17934 messages
2013-05-12 04:31:49ncoghlancreate