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 christian.heimes, gregory.p.smith, vstinner
Date 2019-10-10.18:25:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1570731951.3.0.800765251372.issue38417@roundup.psfhosted.org>
In-reply-to
Content
preexec_fn has been mentally and advisability deprecated for years. :) 
I'll mark it officially with pending deprecation in 3.9 destined to be removed in 3.11.  tracking that in its own rollup issue https://bugs.python.org/issue38435

As far as posix_spawn goes, I expect these kinds of between fork+exec features to be something that prevents posix_spawn from being usable.  As are many other things.  People who want to use posix_spawn will need to know that and seek to avoid those.  That's a documentation issue first and foremost.  Our existing POpen API is very old and wasn't designed to make that nice.

A new API could be made that *only* supports posix_spawn available features if you want an entrypoint that encourages the generally lower latency posix_spawn path.  (A subprocess.spawn function similar to subprocess.run perhaps?)  That should be taken up within its own enhancement issue.
History
Date User Action Args
2019-10-10 18:25:51gregory.p.smithsetrecipients: + gregory.p.smith, vstinner, christian.heimes
2019-10-10 18:25:51gregory.p.smithsetmessageid: <1570731951.3.0.800765251372.issue38417@roundup.psfhosted.org>
2019-10-10 18:25:51gregory.p.smithlinkissue38417 messages
2019-10-10 18:25:51gregory.p.smithcreate