➜

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 barry
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:06:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <2E6BD551-7D54-4358-981C-7FAA5C6BFE94@python.org>
In-reply-to <1559087015.93.0.999902713837.issue33725@roundup.psfhosted.org>
Content 
On May 28, 2019, at 16:43, Ned Deily <report@bugs.python.org> wrote:

> Thanks, I was just going to add that I would accept a doc change for 3.7.  But the wording should be a little clearer that fork has *always* been unsafe on macOS, i.e. this is not a new issue for 3.7 which is one of the reasons it should not be backported.

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.  The problem for Python is that it’s way too easy to do that implicitly, thus causing the macOS to abort the subprocess in surprising ways.
History
Date User Action Args
2019-05-29 00:06:50barrysetrecipients: + barry, gregory.p.smith, ronaldoussoren, pitrou, vstinner, ned.deily, lukasz.langa, josh.r, tdsmith, davin, pablogsal, miss-islington, kapilt
2019-05-29 00:06:50barrylinkissue33725 messages
2019-05-29 00:06:50barrycreate