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, kapilt, miss-islington, ned.deily, pitrou, ronaldoussoren, vstinner
Date 2018-12-13.01:59:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544666393.95.0.788709270274.issue33725@psf.upfronthosting.co.za>
In-reply-to
Content
> Would it be safe to run the multiprocessing tests on recent macOS with the OBJC_DISABLE_INITIALIZE_FORK_SAFETY environment variable set?

See Ronald's reply above in msg331101. I believe his point is that there is nothing you can do to make this safe. And it's not a new problem with 10.14 or 10.13. What is new is that Apple is trying to more forcefully make you aware of the danger by causing the runtime to try to catch and crash these cases earlier rather than permit them to perhaps silently cause failures later.
History
Date User Action Args
2018-12-13 01:59:54ned.deilysetrecipients: + ned.deily, barry, ronaldoussoren, pitrou, vstinner, davin, miss-islington, kapilt
2018-12-13 01:59:53ned.deilysetmessageid: <1544666393.95.0.788709270274.issue33725@psf.upfronthosting.co.za>
2018-12-13 01:59:53ned.deilylinkissue33725 messages
2018-12-13 01:59:52ned.deilycreate