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 pitrou
Recipients davin, pitrou
Date 2017-10-01.12:15:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Looks like this will not make into 3.6.3.

I'd like to sum up the discussion a bit:
- I think at the very least least we must protect the forkserver against SIGINT, like the semaphore tracker already is
- I think it's beneficial to also restart it on demand if necessary
- I can't think of a use case where the user asks "no, please don't restart the forkserver on demand" as there is no way to start it manually anyway, and not restarting it breaks functionality

Also, bpo-31310 is a similar issue for the semaphore tracker.
Date User Action Args
2017-10-01 12:15:27pitrousetrecipients: + pitrou, davin
2017-10-01 12:15:27pitrousetmessageid: <>
2017-10-01 12:15:27pitroulinkissue31308 messages
2017-10-01 12:15:26pitroucreate