➜

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 Matthew Rocklin
Recipients Matthew Rocklin, davin, pitrou
Date 2017-10-16.12:21:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1508156461.69.0.213398074469.issue31308@psf.upfronthosting.co.za>
In-reply-to
Content 
From a user's perspective I would definitely appreciate forkserver being protected from SIGINT.  This bug affects me in practice.  If the forkserver goes down I personally have no objection to it restarting automatically, though I appreciate that I have a narrow view of this topic.

Davin, at your last comment it seemed like you had reservations about this going in.  Did Antoine's recent comments resolve these concerns or no?  Do you have any suggestions on what might be done to protect users from SIGINT crashing the forkserver?
History
Date User Action Args
2017-10-16 12:21:01Matthew Rocklinsetrecipients: + Matthew Rocklin, pitrou, davin
2017-10-16 12:21:01Matthew Rocklinsetmessageid: <1508156461.69.0.213398074469.issue31308@psf.upfronthosting.co.za>
2017-10-16 12:21:01Matthew Rocklinlinkissue31308 messages
2017-10-16 12:21:01Matthew Rocklincreate