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 ggenellina
Recipients castironpi, ggenellina
Date 2008-12-22.03:03:22
SpamBayes Score 4.4775297e-05
Marked as misclassified No
Message-id <1229915004.97.0.528670469965.issue4708@psf.upfronthosting.co.za>
In-reply-to
Content
From the thread in c.l.p: 

Pros (of changing os.pipe() to return inheritable pipes):
 
- as it isn't explicitely documented whether os.pipe() returns 
inheritable pipes or not, both versions are "right" according to the 
documentation.

- if someone relies on pipes being non-inheritable on Windows (why?), 
this is undocumented behaviour, and Python has the right to change it.

- would improve POSIX compatibility, it mimics what os.pipe()
does on those OS

- inheritable pipes are less surprising for guys coming from other OS

- inheritable pipes are a lot more useful than non-inheritable ones 
when doing IPC (probably its main usage).
 
Cons:
 
- os.pipe has behaved that way since long time ago.

- some programs *might* break, if they relied on pipes being 
non-inheritable on Windows, even if that was undocumented behaviour.
History
Date User Action Args
2008-12-22 03:03:25ggenellinasetrecipients: + ggenellina, castironpi
2008-12-22 03:03:24ggenellinasetmessageid: <1229915004.97.0.528670469965.issue4708@psf.upfronthosting.co.za>
2008-12-22 03:03:24ggenellinalinkissue4708 messages
2008-12-22 03:03:23ggenellinacreate