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 eryksun
Recipients Mark.Shannon, eryksun, gvanrossum, miss-islington, paul.moore, serhiy.storchaka, steve.dower, tim.golden, vstinner, zach.ware
Date 2020-11-13.14:08:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1605276497.04.0.935978033731.issue42296@roundup.psfhosted.org>
In-reply-to
Content
> always interrupt and let the thread decide if it has something to do.

SIGNAL_PENDING_CALLS() is called on a Python thread via signal.raise_signal() or _thread.interrupt_main() / PyErr_SetInterrupt(). If you'd rather keep the COMPUTE_EVAL_BREAKER() call in that case, the console control-event case can be distinguished via PyGILState_GetThisThreadState(). It returns NULL if there's no thread state, i.e. WINAPI TlsGetValue returns NULL.
History
Date User Action Args
2020-11-13 14:08:17eryksunsetrecipients: + eryksun, gvanrossum, paul.moore, vstinner, tim.golden, Mark.Shannon, zach.ware, serhiy.storchaka, steve.dower, miss-islington
2020-11-13 14:08:17eryksunsetmessageid: <1605276497.04.0.935978033731.issue42296@roundup.psfhosted.org>
2020-11-13 14:08:17eryksunlinkissue42296 messages
2020-11-13 14:08:16eryksuncreate