STINNER Victor added the comment: > It will be nice, if someone comment that hacks in source code
I don't understand why you keep calling this a hack. It's part of open() contract, and I'm quite sure that it was a deliberate choice to declare O_TMPFILE as O_DIRECTY|new_bit. See for example this comment: https://lwn.net/Articles/560834/ I wrote a patch to explain that it's fine to call open() with O_TMPFILE on old kernels to check if the flag is supported: see attached patch. ---------- resolution: fixed -> status: closed -> open Added file: http://bugs.python.org/file40824/tempfile_comment.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21515> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
