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 eric.snow
Recipients eric.snow, pitrou, vstinner
Date 2018-12-11.21:55:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544565332.64.0.788709270274.issue35423@psf.upfronthosting.co.za>
In-reply-to
Content
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 #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 #33608.
History
Date User Action Args
2018-12-11 21:55:32eric.snowsetrecipients: + eric.snow, pitrou, vstinner
2018-12-11 21:55:32eric.snowsetmessageid: <1544565332.64.0.788709270274.issue35423@psf.upfronthosting.co.za>
2018-12-11 21:55:32eric.snowlinkissue35423 messages
2018-12-11 21:55:32eric.snowcreate