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 r.david.murray
Recipients bukzor, r.david.murray, vstinner
Date 2014-10-24.18:40:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414176021.25.0.0663400551906.issue22722@psf.upfronthosting.co.za>
In-reply-to
Content
pipe2 can also be used to set O_NONBLOCK, so no, that specific API change wouldn't obsolete pipe2.  So, a shim for pipe2 would be the way to go, since that's currently the de-facto standard way of passing flags on pipe creation in unix land.  (The os module is usually a thin layer over OS services...for other modules we might design a more divergent API, but generally in the os module we do not.)
History
Date User Action Args
2014-10-24 18:40:21r.david.murraysetrecipients: + r.david.murray, vstinner, bukzor
2014-10-24 18:40:21r.david.murraysetmessageid: <1414176021.25.0.0663400551906.issue22722@psf.upfronthosting.co.za>
2014-10-24 18:40:21r.david.murraylinkissue22722 messages
2014-10-24 18:40:20r.david.murraycreate