This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jaraco
Recipients jaraco
Date 2010-04-08.01:21:34
SpamBayes Score 0.00024194526
Marked as misclassified No
Message-id <>
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.
Date User Action Args
2010-04-08 01:21:36jaracosetrecipients: + jaraco
2010-04-08 01:21:36jaracosetmessageid: <>
2010-04-08 01:21:34jaracolinkissue8342 messages
2010-04-08 01:21:34jaracocreate