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 John Jones, alex, benjamin.peterson, dhduvall, gennad, gregory.p.smith, martin.panter, miss-islington, ned.deily, neologix, pablogsal, serhiy.storchaka, vstinner
Date 2018-05-04.00:47:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1525394835.65.0.682650639539.issue20104@psf.upfronthosting.co.za>
In-reply-to
Content
Since this is a new API, the most important thing is to have decided how we want it to look in 3.7, it is okay for it to be missing features so long as the API doesn't prevent them from being added in the future.

ie: It is fine to ship it without posix_spawnattr_t attrp "flags" support and without the "p" variant supported in 3.7.

Regarding PR 6693, I agree, keyword only arguments for the flags instead of a sequence of tuples is a good idea.  Since 3.7b4 has shipped I'm not sure we should even consider adding new _features_ to this new API in 3.7 to appear in rc1 - though being entirely new it wouldn't break anything, it just doesn't give us any change to revise them.  I'd be conservative at this point.
History
Date User Action Args
2018-05-04 00:47:16gregory.p.smithsetrecipients: + gregory.p.smith, vstinner, benjamin.peterson, ned.deily, alex, dhduvall, neologix, gennad, martin.panter, serhiy.storchaka, John Jones, pablogsal, miss-islington
2018-05-04 00:47:15gregory.p.smithsetmessageid: <1525394835.65.0.682650639539.issue20104@psf.upfronthosting.co.za>
2018-05-04 00:47:15gregory.p.smithlinkissue20104 messages
2018-05-04 00:47:14gregory.p.smithcreate