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 serhiy.storchaka
Recipients John Jones, alex, benjamin.peterson, dhduvall, gennad, gregory.p.smith, martin.panter, miss-islington, ned.deily, neologix, pablogsal, serhiy.storchaka, vstinner
Date 2018-05-02.06:19:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1525241978.55.0.682650639539.issue20104@psf.upfronthosting.co.za>
In-reply-to
Content
The current implementation looks half-baked to me. It doesn't implement the following features:

1. posix_spawnp(). It is like posix_spawn(), but searches an executable in PATH.

2. Passing various attributes of the created child process. POSIX_SPAWN_SETSIGMASK, POSIX_SPAWN_SETSCHEDPARAM, etc.

And I have doubts about introducing constants like POSIX_SPAWN_OPEN:

1. There is no need to make them integers. They could be strings (for readability) or opaque values.

2. Their names can conflict with future standard constants related to posix_path().

Implementing new features in 3.8 can conflict with the current design. Removing posix_spawn() in 3.7 and deferring the work to 3.8 still looks a better solution to me.
History
Date User Action Args
2018-05-02 06:19:38serhiy.storchakasetrecipients: + serhiy.storchaka, gregory.p.smith, vstinner, benjamin.peterson, ned.deily, alex, dhduvall, neologix, gennad, martin.panter, John Jones, pablogsal, miss-islington
2018-05-02 06:19:38serhiy.storchakasetmessageid: <1525241978.55.0.682650639539.issue20104@psf.upfronthosting.co.za>
2018-05-02 06:19:38serhiy.storchakalinkissue20104 messages
2018-05-02 06:19:38serhiy.storchakacreate