➜

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 vstinner
Recipients gregory.p.smith, pablogsal, serhiy.storchaka, vstinner
Date 2018-09-15.09:10:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1537002609.47.0.956365154283.issue34663@psf.upfronthosting.co.za>
In-reply-to
Content 
Gregory: on Linux, it does change the behavior. The parent blocks until the child is spawned. Python should let the developer decide to opt-in.

Serhiy: IMHO it's better to make posix_spawn() as dumb as possible, a simple wrapper to the C call. use_vfork=True is currently designed for the GNU constant.

posix_spawn(use_vfork=True) raises on FreeBSD: only pass use_vfork=True on Linux.

What do you think?

The problem of changing the default is that we don't know the full list of all platforms that use vfork() by default. If we have a shoet list, how do we know if it's complete? For example, macOS doesn't say anything about vfork. Does it use it? Maybe not. Maybe yes. What if the default changes on a platform?
History
Date User Action Args
2018-09-15 09:10:09vstinnersetrecipients: + vstinner, gregory.p.smith, serhiy.storchaka, pablogsal
2018-09-15 09:10:09vstinnersetmessageid: <1537002609.47.0.956365154283.issue34663@psf.upfronthosting.co.za>
2018-09-15 09:10:09vstinnerlinkissue34663 messages
2018-09-15 09:10:09vstinnercreate