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 ronaldoussoren
Recipients ned.deily, ronaldoussoren, vinay.sajip
Date 2012-07-12.14:47:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1342104421.98.0.940140499192.issue15307@psf.upfronthosting.co.za>
In-reply-to
Content
based on code inspection I'd say that sys.executable was broken without my patch as well. The code that sets that value is unchanged from Python 3.2, and that points to the executable inside the Python.app application bundle.

I've attached v3 of my patch, that ensures that sys.executable is the path used to start the executable. This gives points to the right executable when using venv and is a nicer (and arguably better) result outside of vent's as well.

There should probably be new tests as well that test that sys.executable has the right value in a venv.
History
Date User Action Args
2012-07-12 14:47:02ronaldoussorensetrecipients: + ronaldoussoren, vinay.sajip, ned.deily
2012-07-12 14:47:01ronaldoussorensetmessageid: <1342104421.98.0.940140499192.issue15307@psf.upfronthosting.co.za>
2012-07-12 14:47:01ronaldoussorenlinkissue15307 messages
2012-07-12 14:47:01ronaldoussorencreate