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-19.10:43:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Note that the POSIX_SPAWN_USEVFORK may not do anything at this point (see the link in my previous message, if I read the code correctly POSIX_SPAWN_USEVFORK is no longer used in the implementation of posix_spawn(3)).

Even if it did do something the user that uses the flag needs to evaluate whether or not it is safe to do so, and this requires inspecting the os.posix_spawn implementation and not just the Python code that calls it. 

IMHO we shouldn't expose or use this flag.

If it were useful to do anything with the flag the os.posix_spawn implementation should do so automatically when it is safe to do so (which may require additional steps around calling posix_spawn(3)).
Date User Action Args
2018-09-19 10:43:03ronaldoussorensetrecipients: + ronaldoussoren, gregory.p.smith, vstinner, serhiy.storchaka, pablogsal
2018-09-19 10:43:03ronaldoussorensetmessageid: <>
2018-09-19 10:43:03ronaldoussorenlinkissue34663 messages
2018-09-19 10:43:03ronaldoussorencreate