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 ronaldoussoren
Recipients gregory.p.smith, pablogsal, ronaldoussoren, serhiy.storchaka, vstinner
Date 2018-09-18.19:32:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I get the impression that go uses vfork on Linux, not posix_spawn, because go doesn't use libc (based on reading the referenced issue, not on deep knowledge of go and its implementation).

I do wonder why glibc's implementation of posix_spawn doesn't use vfork more often, and in which cases it is safe to explicitly use vfork even when glibc won't do so by default.

Enabling the use of vfork without determining when it safe to do so is asking for problems, and hard to debug/reproduce ones at that (due to vfork semantics).  Adding a "use_vfork" keyword argument to posix_spawn is IMHO not the right way to go, it would be better to determine when using vfork is safe and then unconditionally enable it.  Otherwise users will have to do the research.
Date User Action Args
2018-09-18 19:32:01ronaldoussorensetrecipients: + ronaldoussoren, gregory.p.smith, vstinner, serhiy.storchaka, pablogsal
2018-09-18 19:32:01ronaldoussorensetmessageid: <>
2018-09-18 19:32:01ronaldoussorenlinkissue34663 messages
2018-09-18 19:32:01ronaldoussorencreate