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 yselivanov
Recipients Arfrever, Jim Fasarakis-Hilliard, Mark.Shannon, benjamin.peterson, cvrebert, daniel.urban, eric.snow, jcea, meador.inge, ncoghlan, njs, yselivanov
Date 2017-05-25.05:17:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Sure. The issue is that I need to mark certain frames as "protected" from KeyboardInterrupt, in a way that my signal handler can see when walking the frame stack, so it can decide whether to raise a KeyboardInterrupt immediately or to wait until a safer moment.

OK, I got it, thanks!

> I suspect the way I'm currently munging frames at runtime also annoys PyPy's JIT.

Yes, whenever you touch frames you're disabling the JIT for the call site (and maybe for more call sites up the stack, idk).  So it doesn't matter what you use, `f_func` or `f_locals`, the performance will suffer big time.  Is that acceptable for Trio?
Date User Action Args
2017-05-25 05:17:04yselivanovsetrecipients: + yselivanov, jcea, ncoghlan, benjamin.peterson, Arfrever, njs, cvrebert, meador.inge, daniel.urban, Mark.Shannon, eric.snow, Jim Fasarakis-Hilliard
2017-05-25 05:17:03yselivanovsetmessageid: <>
2017-05-25 05:17:03yselivanovlinkissue12857 messages
2017-05-25 05:17:03yselivanovcreate