Anyone know this? I’ve never been able to find an answer.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If you’re prone to installing python in various and interesting places on your PATH (as in
$PATHin typical Unix shells,%PATHon typical Windows ones), using/usr/bin/envwill accomodate your whim (well, in Unix-like environments at least) while going directly to/usr/bin/pythonwon’t. But losing control of what version of Python your scripts run under is no unalloyed bargain… if you look at my code you’re more likely to see it start with, e.g.,#!/usr/local/bin/python2.5rather than with an open and accepting#!/usr/bin/env python— assuming the script is important I like to ensure it’s run with the specific version I have tested and developed it with, NOT a semi-random one;-).