[Python-Dev] Warn about mktemp once again? (original) (raw)
David Harrison dave.l.harrison at gmail.com
Tue Apr 29 11:58:39 CEST 2008
- Previous message: [Python-Dev] Warn about mktemp once again?
- Next message: [Python-Dev] Warn about mktemp once again?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 :-)
- Previous message: [Python-Dev] Warn about mktemp once again?
- Next message: [Python-Dev] Warn about mktemp once again?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]