STINNER Victor <vstin...@redhat.com> 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. 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? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33725> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
