[issue12103] Documentation of open() does not claim 'e' support in mode string

STINNER Victor added the comment: Issue #12105 adds os.O_CLOEXEC flag, so we will be able to write open(os.open(filename, os.O_RDONLY|os.O_CLOEXEC)). Do you want to work on a doc patch? -- ___ Python tracker ___

[issue12103] Documentation of open() does not claim 'e' support in mode string

STINNER Victor added the comment: c, e, m and x flags are specific to the GNU libc. Python 2 does basically pass the mode to fopen() unmodified (there is one exception, the U flag). fopen() of Visual C++ 2005 has other flags: c Enable the commit flag for the associated filename so that the co

[issue12103] Documentation of open() does not claim 'e' support in mode string

Changes by Марк Коренберг : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue12103] Documentation of open() does not claim 'e' support in mode string

New submission from Марк Коренберг : open() and friends (like temporaryfile) does not document 'e' letter in second arguement. At least on Linux, it opens file with O_CLOEXEC. Not sure under Windows. Also, there are other interesting letters (man -a fopen), like: c (since glibc 2.3.3) D