[issue8342] Python fails to run if launched from NTFS symlink and DLL not in PATH

2010-04-07 Thread Jason R. Coombs
Jason R. Coombs added the comment: Thanks! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue8342] Python fails to run if launched from NTFS symlink and DLL not in PATH

2010-04-07 Thread Brian Curtin
Brian Curtin added the comment: I have this fixed locally in a version of your os.symlink patch. The solution is to add the directory sys.executable is from to os.environ["Path"], then that test should pass the custom environment when the subprocess is created. I meant to update you on the pa

[issue8342] Python fails to run if launched from NTFS symlink and DLL not in PATH

2010-04-07 Thread Jason R. Coombs
Jason R. Coombs added the comment: This attached patch against the py3k branch adds a test that reproduces the described behavior. -- keywords: +patch Added file: http://bugs.python.org/file16811/reproduction as test.patch ___ Python tracker

[issue8342] Python fails to run if launched from NTFS symlink and DLL not in PATH

2010-04-07 Thread Jason R. Coombs
New submission from Jason R. Coombs : While trying to work out a failing test_platform.PlatformTest.test_architecture_via_symlink, I found a more fundamental problem. In the build environment, python.exe depends on pythonXX.dll being in the same directory as sys.executable to load the interpr