Hi,

tempfile.NamedTemporaryFile provides a good interface
to creating temporary files, but its insistence on
deleting the file upon close is limiting. The attached
patch adds an optional parameter to NamedTemporaryFile
that allows persistence of the temp file after it has
been closed.

One use-case that demonstrates where keeping the
temporary file around is handy would be when you need
to safely create and fill a temp file before it is
atomically moved into place with os.rename(). E.g.

def update_conf(conf_path):
    old = open(conf_path)
    tmp = tempfile.NamedTemporaryFile(prefix =
os.basename(conf_path), \
        dir = os.dirname(conf_path), delete = False)
    for l in old:
        tmp.write(l.replace('war', 'peace'))
    close(old)
    close(tmp)
    os.link(conf_path, conf_path + ".old")
    os.rename(tmp.name, conf_path)

Logged In: YES
user_id=1359232

oops, wrong Category: this should be Lib and not Modules

Logged In: YES
user_id=357491

Why can't you store into an instance of StringIO instead of
a temp file?

Logged In: YES
user_id=1359232

As far as I can tell, StringIO doesn't actually create a
filesystem object that can be manipulated.

Logged In: YES
user_id=1359232

Here is an diff that includes a regress test

Logged In: YES
user_id=357491

Right, it doesn't create a filesystem file. But that is the
point. You work in memory and then write to your final
destination as needed. Your code you have pasted in the
description does nothing special that requires the use of a
temporary file. You can just write into a StringIO object,
skip the os.link call, and then just write out to the final
file location.

Logged In: YES
user_id=1359232

Well, that would a) not be an atomic replacement and b) you
miss (or would have to reimplement) the mkstemp() like
behaviour.

Thanks for the patch, committed with doc changes as rev. 54344.