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 davin
Recipients davin, pitrou
Date 2017-09-11.03:43:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I have two concerns with this:
1) The implicit restart of the forkserver process seems in conflict with the zen of making things explicit.
2) This would seem to make forkserver's behavior inconsistent with the behavior of things like the Manager which similarly creates its own process for managing resources but does not automatically restart that process if it should die or become unreachable.  In the case of the Manager, I don't think we'd want it to automagically restart anything in these situations so it's not a simple matter of enhancing the Manager to adopt similar behavior.

I do appreciate the use cases that would be addressed by having a convenient way to detect that a forkserver has died and then restart it.  If the forkserver dies, I doubt we really want it to try to restart a potentially infinite number of times.

Maybe a better path would be if we had a way to explicitly request that the Process trigger a restart of the forkserver, if necessary, but this setting/request defaults to False?
Date User Action Args
2017-09-11 03:43:59davinsetrecipients: + davin, pitrou
2017-09-11 03:43:59davinsetmessageid: <>
2017-09-11 03:43:59davinlinkissue31308 messages
2017-09-11 03:43:59davincreate