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 xdegaye
Recipients xdegaye
Date 2014-08-05.20:39:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1407271163.94.0.203518620414.issue22149@psf.upfronthosting.co.za>
In-reply-to
Content
When tracing, the frame of a suspended generator should not have an f_trace function as there is no way to delete the frame f_trace attribute in that case even though
tracing may have been disabled.

The patch relies on the fact that whenever the generator is resumed, a 'call' tracing event is issued and the generator's frame f_trace is set again.
As expected, frames, including generators' frames, have their f_trace attribute cleared on the 'return' tracing event that is issued when the frame goes out of scope
or when the system's trace function has been removed.
History
Date User Action Args
2014-08-05 20:39:23xdegayesetrecipients: + xdegaye
2014-08-05 20:39:23xdegayesetmessageid: <1407271163.94.0.203518620414.issue22149@psf.upfronthosting.co.za>
2014-08-05 20:39:23xdegayelinkissue22149 messages
2014-08-05 20:39:23xdegayecreate