You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
assignee=Noneclosed_at=<Date2013-08-16.12:56:28.826>created_at=<Date2013-08-06.19:43:40.136>labels= ['easy', 'type-feature', 'library']
title='Add O_TMPFILE to os module'updated_at=<Date2015-10-19.21:18:27.991>user='https://github.com/tiran'
Quote from http://lwn.net/Articles/557314/
The new O_TMPFILE option to the open() and openat() system calls allows filesystems to optimize the creation of temporary files — files which need not be visible in the filesystem. When O_TMPFILE is present, the provided pathname is only used to locate the containing directory (and thus the filesystem where the temporary file should be). So, among other things, programs using O_TMPFILE should have fewer concerns about vulnerabilities resulting from symbolic link attacks.
add O_TEMPFILE to posixmodule.c
use O_TEMPFILE in tempfile module when it's supported by the current kernel
I like to hold off with the actual use of O_TMPFILE in tempfile until Python 3.5. The feature is too new and I don't have any way to test it. Some people have reported file system corruption in 3.11-rc4, too.