Antoine Pitrou <pit...@free.fr> added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31308> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
