This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients dloewenherz, ezio.melotti, serhiy.storchaka, terry.reedy
Date 2013-08-17.19:59:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1376769560.06.0.268568233103.issue18730@psf.upfronthosting.co.za>
In-reply-to
Content
'Filename extensions' are a proper subset of 'suffixes'.
https://en.wikipedia.org/wiki/Filename_extension
Dan 'solutions' indicates that he thinks that the two sets are or should be the same, which they are not. The only thing that is DOS/Windows specific is its more special treatment of '.'.  That said, I can see how a Windows user might be confused by the following awkward sentence.

    If 'suffix' is specified, the file name will end with that suffix,
    otherwise there will be no suffix.

as 'no suffix' is easily read as 'no extension. The manual, but not the docstring, addresses the possible confusion by adding

  mkstemp() does not put a dot between the file name and the suffix;
  if you need one, put it at the beginning of suffix.

I think the prefix sentence is also a bit awkward.

    If 'prefix' is specified, the file name will begin with that prefix,
    otherwise a default prefix is used.

I think both parameters should be explained in both docstring and doc with one shorter and clearer entry.

"The file name will begin with *prefix* (default 'tmp') and end with *suffix* (default ''). The is no automatic addition of a period ('.') before the suffix."
History
Date User Action Args
2013-08-17 19:59:20terry.reedysetrecipients: + terry.reedy, ezio.melotti, dloewenherz, serhiy.storchaka
2013-08-17 19:59:20terry.reedysetmessageid: <1376769560.06.0.268568233103.issue18730@psf.upfronthosting.co.za>
2013-08-17 19:59:20terry.reedylinkissue18730 messages
2013-08-17 19:59:19terry.reedycreate