Message 303458 - Python tracker

➜

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	<1506860127.02.0.213398074469.issue31308@psf.upfronthosting.co.za>
In-reply-to

Content
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.

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.

History
Date	User	Action	Args
2017-10-01 12:15:27	pitrou	set	recipients: + pitrou, davin
2017-10-01 12:15:27	pitrou	set	messageid: <1506860127.02.0.213398074469.issue31308@psf.upfronthosting.co.za>
2017-10-01 12:15:27	pitrou	link	issue31308 messages
2017-10-01 12:15:26	pitrou	create