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 vstinner
Recipients Mark.Shannon, corona10, eric.snow, gvanrossum, kj, vstinner
Date 2022-01-23.13:52:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Signal handling in Python is asynchronous.

See my previous comment: "CHECK_EVAL_BREAKER() matters for signals, but also multithreading (drop the GIL), asynchronous exception and pending calls."

If a thread executes a function which only uses opcodes which don't call CHECK_EVAL_BREAKER(), I understand that it can eat more than its slice of 5 ms, see sys.getswitchinterval():

So it's also a threads scheduling issue, no?
Date User Action Args
2022-01-23 13:52:56vstinnersetrecipients: + vstinner, gvanrossum, Mark.Shannon, eric.snow, corona10, kj
2022-01-23 13:52:56vstinnersetmessageid: <>
2022-01-23 13:52:56vstinnerlinkissue46465 messages
2022-01-23 13:52:56vstinnercreate