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 Elad Lahav
Recipients Elad Lahav, dstufft, eric.araujo, gvanrossum, p-ganssle, pitrou, vstinner
Date 2020-02-26.20:10:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1582747806.61.0.29363182759.issue39763@roundup.psfhosted.org>
In-reply-to
Content
I'm not convinced that a multi-threaded fork()+exec() from C would be any better, unless the Python code goes to great lengths to avoid any non-async-signal-safe operations between the fork() and the exec().
So along with the proposed change to switch to the subprocess() module I would like to propose that that module switch to using posix_spawn() instead of fork()+exec().
History
Date User Action Args
2020-02-26 20:10:06Elad Lahavsetrecipients: + Elad Lahav, gvanrossum, pitrou, vstinner, eric.araujo, dstufft, p-ganssle
2020-02-26 20:10:06Elad Lahavsetmessageid: <1582747806.61.0.29363182759.issue39763@roundup.psfhosted.org>
2020-02-26 20:10:06Elad Lahavlinkissue39763 messages
2020-02-26 20:10:06Elad Lahavcreate