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;-).
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…