Antoine Pitrou added the comment: > Mostly looks good to me, but I think I'd prefer that attempts to clear > a running frame raise RuntimeError with an appropriate message.
Hmm, why not. My intuition was to make frame.clear() a best-effort method, but this sounds ok too. > 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. Yes, perhaps. Then Eric's patch can incorporate that change once the frame.clear() patch is committed. > (We may want to add a "clear_frames" convenience method to tracebacks > as well) That, or in the traceback module. The reason I'm proposing this one as a frame method is that it can't be done in pure Python. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17934> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
