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 ned.deily
Recipients barry, davin, gregory.p.smith, josh.r, kapilt, lukasz.langa, miss-islington, ned.deily, pablogsal, pitrou, ronaldoussoren, tdsmith, vstinner
Date 2019-05-29.00:39:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> To be clear, what is unsafe on macOS (as of 10.13, but even more so on 10.14) is calling into the Objective-C runtime between fork and exec.

No, it has *always* been unsafe. What's new as of 10.13/14 is that macOS tries much harder at runtime to detect such cases and more predictably cause an error rather than let the process run on and possibly fail nondeterministically. 

> Do only a few Python module use the Objective-C runtime? Or is it basically "everything"?

I don't think we should try to second-guess this.  We now recognize that using fork like this on macOS has always been dangerous.  For some programs it will be fine, for others it won't.  People have had many macOS and Python releases to deal with this; if it works for their application, we shouldn't be changing the default for them.  But let's make it easier for new users to do the right thing - first by documenting the pitfall, then, in 3.8, changing the default.
Date User Action Args
2019-05-29 00:39:36ned.deilysetrecipients: + ned.deily, barry, gregory.p.smith, ronaldoussoren, pitrou, vstinner, lukasz.langa, josh.r, tdsmith, davin, pablogsal, miss-islington, kapilt
2019-05-29 00:39:36ned.deilysetmessageid: <>
2019-05-29 00:39:36ned.deilylinkissue33725 messages
2019-05-29 00:39:36ned.deilycreate