Changes by Jason Day <[EMAIL PROTECTED]>:
--
title: ntpath.abspath can fail on Win Server 2008 (64-bit) -> ntpath.abspath
fails for long str paths
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Jason Day <[EMAIL PROTECTED]> added the comment:
> Indeed. Do you happen to have the complete traceback of the failing
> tempfile.mktemp() call? I don't see where it can use the PATH
> environment variable.
The problem was that somehow, on our systems, the TEMP environmenta
Changes by Jason Day <[EMAIL PROTECTED]>:
--
title: ntpath.abspath can fail on Win Server 2008 (64-bit) -> ntpath.abspath
fails for long str paths
___
Python tracker <[EMAIL PROTECTED]>
<http://bugs.py
Jason Day <[EMAIL PROTECTED]> added the comment:
> I am not sure to understand. Do you mean the whole PATH environment
> variable? I doubt that it is passed to _getfullpathname.
> Or do you have very long paths for one directory? the TEMP environment
> variable, for example?
Jason Day <[EMAIL PROTECTED]> added the comment:
Running help() or mktemp() causes _getfullpathname to be called with the whole
system path (791 characters). If you pass that to _getfullpathname as str it
throws the aforementioned TypeError. If it's passed as unicode, it return
New submission from Jason Day <[EMAIL PROTECTED]>:
On my system (Windows Server 2008 SP1 - 64-bit, Python 2.5.2 - 32-bit),
simple actions like:
>>> help(help) # Or any function
or
>>> import tempfile
>>> f = tempfile.mktemp()
result in this (rather confusing) e
