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 gregory.p.smith
Recipients gregory.p.smith, izbyshev, nanjekyejoannah, pablogsal, pitrou, serhiy.storchaka, vstinner
Date 2018-12-26.22:36:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Thanks for all your research and reference links on this!  As a _posixsubprocess maintainer, I am not against either posix_spawn or vfork being used directly in the future when feasible.

A challenge, especially with platform specific vfork, is making sure we understand exactly which platforms it can work properly on and checking for those both at compile time _and_ runtime (running kernel version and potentially the runtime libc version?) so that we can only use it in situations we are sure it is supposed to behave as desired in.  My guiding philosophy: Be conservative on choosing when such a thing is safe to use.
Date User Action Args
2018-12-26 22:36:23gregory.p.smithsetrecipients: + gregory.p.smith, pitrou, vstinner, serhiy.storchaka, izbyshev, pablogsal, nanjekyejoannah
2018-12-26 22:36:21gregory.p.smithsetmessageid: <>
2018-12-26 22:36:21gregory.p.smithlinkissue35537 messages
2018-12-26 22:36:21gregory.p.smithcreate