[issue14243] NamedTemporaryFile usability request

2012-03-09 Thread Dave Abrahams

New submission from Dave Abrahams d...@boostpro.com:

NamedTemporaryFile is too hard to use portably when you need to open the file 
by name after writing it.  To do that, you need to close the file first (on 
Windows), which means you have to pass delete=False, which in turn means that 
you get no help in cleaning up the actual file resource, which as you can see 
from the code in tempfile.py is devilishly hard to do correctly.  The fact that 
it's different on posix (you can open the file for reading by name without 
closing it first) makes this problem worse. What we really need for this 
use-case is a way to say, delete on __del__ but not on close().

--
components: Library (Lib)
messages: 155278
nosy: dabrahams
priority: normal
severity: normal
status: open
title: NamedTemporaryFile usability request
versions: Python 2.7

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14243
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue14243] NamedTemporaryFile usability request

2012-03-09 Thread Eric V. Smith

Changes by Eric V. Smith e...@trueblade.com:


--
nosy: +eric.smith

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14243
___
___
Python-bugs-list mailing list
Unsubscribe: 
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com