You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a while now the signal handling machinery has piggy-backed on ceval's "pending calls" machinery (e.g. Py_AddPendingCall). This is a bit confusing. It also increases the risk with unrelated changes to the pending calls code.
Correct. The remaining call to Py_AddPendingCall in the signal-handling code is fine.
This issue is only indirectly related. I suppose you could consider it a follow-up to bpo-30703. The PR for that issue (GH-2415) switches from using pending calls for signal handlers to using the pending calls machinery without actual pending calls.
So here I want to address taking the next step: deal with pending signals separately from pending calls. That separation helps simplify efforts to adapt the pending calls machinery for use in arbitrary threads (rather than the main thread). See bpo-33608.