Author neologix
Recipients alexey-smirnov, amaury.forgeotdarc, christian.heimes, neologix, pitrou, rosslagerwall, sbt, vstinner
Date 2013-01-04.13:27:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM35utUG-_HtDoQu48MiFouDT8G=FWc4rXSE6FfWRaVaWQ@mail.gmail.com>
In-reply-to <1357256574.93.0.873081663094.issue16850@psf.upfronthosting.co.za>
Content
> Windows provides O_NOINHERIT (_O_NOINHERIT) flag which has a similar purpose.
>
>> ... and even then, many Unices don't support it.
>
> Yes, but I bet that more and more OSes will support it :-) For example, it looks like O_CLOEXEC is part of the POSIX standard 2008:

Hum, OK, but many operating systems don't support it to this day.
So if we expose it and the underlying operating system doesn't support
it, do you want to fallback to fcntl (which wouldb't be atomic
anymore, but let's pretend the GIL protection is enough).

Also, I'm not sure exactly if this flag is useful enough to be
exposed: there are many flags that can be passed when opening a file:
O_DIRECT, O_SYNC, O_NONBLOCK, O_DSYNC...
Amusingly, Java exposes some of them (but not O_CLOEXEC):
http://docs.oracle.com/javase/7/docs/api/java/nio/file/StandardOpenOption.html
History
Date User Action Args
2013-01-04 13:27:52neologixsetrecipients: + neologix, amaury.forgeotdarc, pitrou, vstinner, christian.heimes, rosslagerwall, sbt, alexey-smirnov
2013-01-04 13:27:52neologixlinkissue16850 messages
2013-01-04 13:27:51neologixcreate