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 paul.moore
Recipients paul.moore, vinay.sajip
Date 2013-05-04.10:12:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1367662362.6.0.575670511803.issue17903@psf.upfronthosting.co.za>
In-reply-to
Content
The Python launcher for windows should recognise a hashbang line of #!/usr/bin/env python, and use the python executable found on PATH to run the script. If no python executable is present on PATH the launcher should fall back to the current behaviour (using the default python, as if #!/usr/bin/python were present).

This matches the behaviour on other platforms where env is used to ensure that the script uses the user's currently activated Python, and is particularly important when virtualenvs are being used.
History
Date User Action Args
2013-05-04 10:12:42paul.mooresetrecipients: + paul.moore, vinay.sajip
2013-05-04 10:12:42paul.mooresetmessageid: <1367662362.6.0.575670511803.issue17903@psf.upfronthosting.co.za>
2013-05-04 10:12:42paul.moorelinkissue17903 messages
2013-05-04 10:12:42paul.moorecreate