[issue4071] ntpath.abspath can fail on Win Server 2008 (64-bit)

2008-10-08 Thread Jason Day
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 environmental variable had been c

[issue4071] ntpath.abspath can fail on Win Server 2008 (64-bit)

2008-10-08 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: > I don't have it offhand, but it was the whole PATH environment > variable, complete with semicolons. That's probably the *real* bug. Indeed. Do you happen to have the complete traceback of the failing tempfile.mktemp() call? I don't

[issue4071] ntpath.abspath can fail on Win Server 2008 (64-bit)

2008-10-08 Thread Jason Day
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? I'd be curious to see

[issue4071] ntpath.abspath can fail on Win Server 2008 (64-bit)

2008-10-08 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: > Running help() or mktemp() causes _getfullpathname to be called > with the whole system path (791 characters) I am not sure to understand. Do you mean the whole PATH environment variable? I doubt that it is passed to _getfullpathname

[issue4071] ntpath.abspath can fail on Win Server 2008 (64-bit)

2008-10-07 Thread Hirokazu Yamamoto
Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: According to http://msdn.microsoft.com/en-us/library/aa364963.aspx, current implementation have several problems. >In the ANSI version of this function, the name is limited to MAX_PATH >characters. To extend this limit to 32,767 wide chara

[issue4071] ntpath.abspath can fail on Win Server 2008 (64-bit)

2008-10-07 Thread Jason Day
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 returns an empty strin

[issue4071] ntpath.abspath can fail on Win Server 2008 (64-bit)

2008-10-07 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: The (buffer overflow) message indicates that the argument is too long to be converted. In your case, it seems that the path is longer than MAX_PATH=255 characters. What is the value of the argument of _getfullpathname()? -- n

[issue4071] ntpath.abspath can fail on Win Server 2008 (64-bit)

2008-10-07 Thread Jason Day
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) error: TypeError: _getfullpathname()