New submission from Jason R. Coombs <jar...@jaraco.com>: 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 interpreter. If Python is launched from an NTFS symlink, sys.executable may be located in a directory other than the DLL, and the interpreter fails to run (returning exit code 0xC0000135). This may be expected behavior, but it causes test_architecture_via_symlink to fail once Python becomes aware of symlinks in Windows (sans cygwin). It took me a while to track this down, so I wanted to be sure to document the behavior. ---------- components: Tests, Windows messages: 102584 nosy: jaraco severity: normal status: open title: Python fails to run if launched from NTFS symlink and DLL not in PATH versions: Python 3.1, Python 3.2 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8342> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
