Issue #26261: Clarify NamedTemporaryFile name attribute vs file.name
This commit is contained in:
parent
3e85838ee9
commit
be9ddc1d11
|
@ -64,7 +64,8 @@ The module defines the following user-callable functions:
|
|||
This function operates exactly as :func:`TemporaryFile` does, except that
|
||||
the file is guaranteed to have a visible name in the file system (on
|
||||
Unix, the directory entry is not unlinked). That name can be retrieved
|
||||
from the :attr:`name` attribute of the file object. Whether the name can be
|
||||
from the :attr:`name` attribute of the returned
|
||||
file-like object. Whether the name can be
|
||||
used to open the file a second time, while the named temporary file is
|
||||
still open, varies across platforms (it can be so used on Unix; it cannot
|
||||
on Windows NT or later). If *delete* is true (the default), the file is
|
||||
|
|
|
@ -455,8 +455,8 @@ def NamedTemporaryFile(mode='w+b', bufsize=-1, suffix="",
|
|||
The file is created as mkstemp() would do it.
|
||||
|
||||
Returns an object with a file-like interface; the name of the file
|
||||
is accessible as file.name. The file will be automatically deleted
|
||||
when it is closed unless the 'delete' argument is set to False.
|
||||
is accessible as its 'name' attribute. The file will be automatically
|
||||
deleted when it is closed unless the 'delete' argument is set to False.
|
||||
"""
|
||||
|
||||
if dir is None:
|
||||
|
|
Loading…
Reference in New Issue