[Peter Hansen]
>>> What I don't understand is why you _can't_ reopen the NamedTemporaryFile
>>> under Windows when you can reopen the file created by mkstemp (and the
>>> files created by TemporaryFile are created by mkstemp in the first place).
[Lee Harr]
>> Are you saying you tried it and you ac
Lee Harr wrote:
> On 2005-12-29, Peter Hansen <[EMAIL PROTECTED]> wrote:
>>What I don't understand is why you _can't_ reopen the NamedTemporaryFile
>>under Windows when you can reopen the file created by mkstemp (and the
>>files created by TemporaryFile are created by mkstemp in the first place).
On Thu, Dec 29, 2005 at 12:40:34AM -0500, Peter Hansen wrote:
>
> What I don't understand is why you _can't_ reopen the NamedTemporaryFile
> under Windows when you can reopen the file created by mkstemp (and the
> files created by TemporaryFile are created by mkstemp in the first place).
Basica
On 2005-12-29, Peter Hansen <[EMAIL PROTECTED]> wrote:
> Lee Harr wrote:
>> Is there any other reason to use a named tempfile other than
>> to be able to open it again?
> As it says, if you *don't close* the file, you can open it again if you
> are on a platform which supports that.
>
Ok. I just
Lee Harr wrote:
> Is there any other reason to use a named tempfile other than
> to be able to open it again? I am trying to understand this
> section of the documentation regarding NamedTemporaryFile:
>
> """
> Whether the name can be used to open the file a second time, while the named
> tempor
Is there any other reason to use a named tempfile other than
to be able to open it again? I am trying to understand this
section of the documentation regarding NamedTemporaryFile:
"""
Whether the name can be used to open the file a second time, while the named
temporary file
is still open, var
