[issue19056] Windows 7, script exec not working without explicit cal of python.exe

2013-09-21 Thread Eric V. Smith
Eric V. Smith added the comment: Glad to see it's working. -- resolution: fixed -> invalid stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___

[issue19056] Windows 7, script exec not working without explicit cal of python.exe

2013-09-21 Thread Thierry Seunevel
Thierry Seunevel added the comment: Many thanks for your answers. printing the sys.path gave me this output (parsed with newlines) '', 'D:\\soft\\python\\lib', 'D:\\Thierry\\python\\d\\thierry\\python', < mispelled 'C:\\Windows\\system32\\python27.zip', 'd:\\soft\\python\\DLLs', 'd:\\soft\\

[issue19056] Windows 7, script exec not working without explicit cal of python.exe

2013-09-20 Thread Ned Deily
Ned Deily added the comment: You may have a mismatch with two different versions of Python 2.7 installed. Issue18050 documents the basic problem: a change introduced in Python 2.7.4 causes problems if a pre-2.7.4 interpreter executable is launched with a 2.7.4 or later Python standard library

[issue19056] Windows 7, script exec not working without explicit cal of python.exe

2013-09-20 Thread Eric V. Smith
Eric V. Smith added the comment: Can you print out sys.executable and sys.path in both cases, and post the results here? -- nosy: +eric.smith ___ Python tracker ___

[issue19056] Windows 7, script exec not working without explicit cal of python.exe

2013-09-20 Thread Thierry Seunevel
New submission from Thierry Seunevel: Executing a script from the command prompt works if Python.exe called explicitly, doesn't work if script name only. Example : python.exe script.py is ok script.py gives the following : Traceback (most recent call last): File "D:\soft\python\lib\site.py", l