➜

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 Mark.Shannon, deleted0524, jdemeyer, ncoghlan, njs, yselivanov
Date 2017-06-28.12:55:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1498654541.42.0.431145188928.issue29988@psf.upfronthosting.co.za>
In-reply-to
Content 
One testing possibility worth considering: perhaps it would be make sense to have "start_try" and "start_finally" trace events, such that a trace function could be installed that injected signals at the worst possible time in the opcode evaluation?

I haven't fully thought through the possible implications of that approach, but it seems like it would be less fragile than counting code offsets.
History
Date User Action Args
2017-06-28 12:55:41ncoghlansetrecipients: + ncoghlan, njs, Mark.Shannon, jdemeyer, yselivanov, deleted0524
2017-06-28 12:55:41ncoghlansetmessageid: <1498654541.42.0.431145188928.issue29988@psf.upfronthosting.co.za>
2017-06-28 12:55:41ncoghlanlinkissue29988 messages
2017-06-28 12:55:41ncoghlancreate