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 vstinner
Recipients docs@python, eric.araujo, socketpair, vstinner
Date 2013-01-03.15:33:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1357227223.63.0.929012376696.issue12103@psf.upfronthosting.co.za>
In-reply-to
Content
> x      Open the file exclusively (like the O_EXCL flag of open(2)).
>  If the  file  already exists, fopen() fails, and sets errno to EEXIST.
> This flag is ignored for fdopen().

Python 3.3 adds support for this mode: see issue #12760.

> e (since glibc 2.7)
>       Open  the  file  with  the O_CLOEXEC flag.  See open(2) for more information.

I created the issue #16850 for this mode.

--

Other modes seem to be very specific to some platforms. I don't think that it would be possible to expose them in a portable way using the open() function directly.

Can we close this issue? I prefer to work on #16850 for the close-on-exec mode.
History
Date User Action Args
2013-01-03 15:33:43vstinnersetrecipients: + vstinner, eric.araujo, docs@python, socketpair
2013-01-03 15:33:43vstinnersetmessageid: <1357227223.63.0.929012376696.issue12103@psf.upfronthosting.co.za>
2013-01-03 15:33:43vstinnerlinkissue12103 messages
2013-01-03 15:33:43vstinnercreate