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 steve.dower
Recipients carljm, corona10, dino.viehland, eelizondo, gregory.p.smith, nascheme, pablogsal, pitrou, shihai1991, steve.dower, tim.peters, vstinner
Date 2020-04-15.22:09:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1586988573.5.0.623229954189.issue40255@roundup.psfhosted.org>
In-reply-to
Content
> What problem do you have in mind that the fork server would solve?

My understanding is that the fork server solves the *general* problem of running arbitrary code before fork by making sure that only CPython/multiprocessing gets to run code before fork.

In this specific case where you're carefully running only forkable code at startup, it presumably won't help.
History
Date User Action Args
2020-04-15 22:09:33steve.dowersetrecipients: + steve.dower, tim.peters, nascheme, gregory.p.smith, pitrou, vstinner, carljm, dino.viehland, corona10, pablogsal, eelizondo, shihai1991
2020-04-15 22:09:33steve.dowersetmessageid: <1586988573.5.0.623229954189.issue40255@roundup.psfhosted.org>
2020-04-15 22:09:33steve.dowerlinkissue40255 messages
2020-04-15 22:09:33steve.dowercreate