GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • [Python-Dev] Warn about mktemp once again?
  • [Python-Dev] Warn about mktemp once again?
  • [ date ]
  • [ thread ]
  • [ subject ]
  • [ author ]

This view

  • Original page
  • New address

GeezerVison is showing mail.python.org — [Python-Dev] Warn about mktemp once again?

[Python-Dev] Warn about mktemp once again?

skip at pobox.com skip at pobox.com
Thu May 8 03:47:44 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 ]

This has been a fairly interesting discussion about tempfile.mktemp, but can
we return to the original question?  Should we begin warning about its use
again?  Should we ever warn about it?  It appears that NamedTemporaryFile
gives you a reasonable (secure) replacement.  I'm happy to document
mktemp->NamedTemporaryFile with an example in tempfile.rst if that's what it
will take.  Before knowing about the delete=False parameter I proposed a
mkstempf() function, whose tracker issue I will close if that hasn't already
happened.

Skip

  • 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 ]

More information about the Python-Dev mailing list
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.