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.17:04:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <BEDC1C18-F73B-468F-93BE-AEEAEAB33407@python.org>
In-reply-to <1559090291.0.0.812534160773.issue33725@roundup.psfhosted.org>
Content
On May 28, 2019, at 17:38, Ned Deily <report@bugs.python.org> wrote:
> 
> Ned Deily <nad@python.org> added the comment:
> 
>> 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 letter than let the process run on and possibly fail nondeterministically.

Right, thanks for the additional nuance.  I think what changed is that in 10.13, Apple added a warning output when this condition occurred, and in 10.14 they actually abort the subprocess.
History
Date User Action Args
2019-05-29 17:04:10barrysetrecipients: + barry, gregory.p.smith, ronaldoussoren, pitrou, vstinner, ned.deily, lukasz.langa, josh.r, tdsmith, davin, pablogsal, miss-islington, kapilt
2019-05-29 17:04:10barrylinkissue33725 messages
2019-05-29 17:04:09barrycreate