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 vstinner, xdegaye
Date 2014-02-14.17:44:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1392399862.03.0.743137094054.issue20601@psf.upfronthosting.co.za>
In-reply-to
Content
With the previous patch, after the signal arrives and the first call to PyErr_CheckSignals, PyErr_CheckSignals is called for each bytecode processed in the eval loop
of the tracing function (and the eval loop of functions called by the tracing function, and also functions called in the other threads).
This is annoying. The attached patch fixes this and adds a test case.
History
Date User Action Args
2014-02-14 17:44:22xdegayesetrecipients: + xdegaye, vstinner
2014-02-14 17:44:22xdegayesetmessageid: <1392399862.03.0.743137094054.issue20601@psf.upfronthosting.co.za>
2014-02-14 17:44:22xdegayelinkissue20601 messages
2014-02-14 17:44:21xdegayecreate