[Python-Dev] Warn about mktemp once again?

Nick Coghlan ncoghlan at gmail.com
Tue Apr 29 14:18:16 CEST 2008

David Harrison wrote:
> 2008/4/29 "Martin v. Löwis" <martin at v.loewis.de>:
>>> Same here. In fact, is there a good reason to have mkstemp() return the
>>  > fd (except backward compatibility)?
>>  Except for backwards compatibility: is there a good reason to keep
>>  os.mkstemp at all?
> Greg Ewing's use-case is one I've also had at times - ie. as a
> convenience function for creating a "somewhat temporary" file that is
> randomly named, but persists beyond the closing of the file.  If the
> function doesn't stay in os it doesn't make any difference to me
> though :-)

As of 2.6, Greg's use case is addressed by the new 'delete' parameter on 

The implementation of the tempfile module uses os.mkstemp() though, so 
getting rid of the latter might cause a few problems :)


Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia

More information about the Python-Dev mailing list