71
votes

Anyone know this? I've never been able to find an answer.

5
not a ton. i'm on osx and the env manpage is rather ambiguous there. - Kenneth Reitz
@S.Lott: Have you read it lately? On my Debian box, it's one of the most unhelpful man pages I've ever seen, and that's saying something. (Here's the whole "Description": Set each NAME to VALUE in the environment and run COMMAND. Yup, that would clear him right up.) - Telemachus
@Telemachus: Yes, I did read it. It's why I found the Wikipedia entry. - S.Lott
One problem with env is that you can't add -u or any other option to be passed to the python executable - Arkady
Also a very good answer on a very related Unix SE question is here. - Albert

5 Answers

67
votes

If you're prone to installing python in various and interesting places on your PATH (as in $PATH in typical Unix shells, %PATH on typical Windows ones), using /usr/bin/env will accomodate your whim (well, in Unix-like environments at least) while going directly to /usr/bin/python won'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.5 rather 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;-).

24
votes

From wikipedia

Shebangs specify absolute paths to system executables; this can cause problems on systems which have non-standard file system layouts

Often, the program /usr/bin/env can be used to circumvent this limitation

10
votes

it finds the python executable in your environment and uses that. it's more portable because python may not always be in /usr/bin/python. env is always located in /usr/bin.

5
votes

It finds 'python' also in /usr/local/bin, ~/bin, /opt/bin, ... or wherever it may hide.