Message 343842 - Python tracker

➜

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.

In-reply-to
Author	vstinner
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:21:33
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1559089293.33.0.822605654905.issue33725@roundup.psfhosted.org>

Content
> 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. Do only a few Python module use the Objective-C runtime? Or is it basically "everything"? If it's just a few, would it be possible to emit a warning or even an exception if called in a child process after fork?

Content

> 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.
Do only a few Python module use the Objective-C runtime? Or is it basically "everything"?
If it's just a few, would it be possible to emit a warning or even an exception if called in a child process after fork?

History
Date	User	Action	Args
2019年05月29日 00:21:33	vstinner	set	recipients: + vstinner, barry, gregory.p.smith, ronaldoussoren, pitrou, ned.deily, lukasz.langa, josh.r, tdsmith, davin, pablogsal, miss-islington, kapilt
2019年05月29日 00:21:33	vstinner	set	messageid: <1559089293.33.0.822605654905.issue33725@roundup.psfhosted.org>
2019年05月29日 00:21:33	vstinner	link	issue33725 messages
2019年05月29日 00:21:33	vstinner	create

homepage