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 Arfrever, georg.brandl, josh.r, ncoghlan, neologix, pitrou, python-dev, serhiy.storchaka, socketpair, vstinner
Date 2015-10-20.19:39:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1445369990.52.0.181711076719.issue21515@psf.upfronthosting.co.za>
In-reply-to
Content
> 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.
History
Date User Action Args
2015-10-20 19:39:50vstinnersetrecipients: + vstinner, georg.brandl, ncoghlan, pitrou, Arfrever, neologix, socketpair, python-dev, serhiy.storchaka, josh.r
2015-10-20 19:39:50vstinnersetmessageid: <1445369990.52.0.181711076719.issue21515@psf.upfronthosting.co.za>
2015-10-20 19:39:50vstinnerlinkissue21515 messages
2015-10-20 19:39:50vstinnercreate