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 ned.deily
Recipients ned.deily, ronaldoussoren, vinay.sajip
Date 2012-07-13.07:32:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1342164739.41.0.616761640927.issue15307@psf.upfronthosting.co.za>
In-reply-to
Content
Fixing sys.executable to point to the stub launcher instead of the interpreter in the fw will also fix other unrelated issues, like making python3-32 work properly in 64-/32-bit builds for IDLE and for tests that spawn interpreters in subprocesses.  Today, while the main process is 32-bit,  the interpreters in subprocesses are 64-bit.

I did a little clean up and fixed up the documentation somewhat; see the revised patch.  But building a stock installer and running the tests showed two issues:
1) test_osx_env fails at line 28, checking PYTHONEXECUTABLE
2) when running the tests within a venv, test_venv now fails at line 95;
sys.baseprefix != sys.prefix.  This did not fail previously

Also, I saw another test failure when building and running with a test framework environment that included a relative link.  It appeared that _NSGetExecutablePath in pythonw.c returned an unnormalized path:
>>> sys.executable
'/py/dev/default/b10.7_t10.7_x4.3_cclang_d/fw/./root/bin/python3.3'
which caused a test_venv failure.  I probably won't have time to look at this again for a few days.
History
Date User Action Args
2012-07-13 07:32:19ned.deilysetrecipients: + ned.deily, vinay.sajip, ronaldoussoren
2012-07-13 07:32:19ned.deilysetmessageid: <1342164739.41.0.616761640927.issue15307@psf.upfronthosting.co.za>
2012-07-13 07:32:18ned.deilylinkissue15307 messages
2012-07-13 07:32:18ned.deilycreate