What's the difference between python shebangs with /usr/bin/env rather than hard-path?

python path environment shebang
Ken picture Ken · Apr 19, 2011 · Viewed 19.7k times · Source

I used to use the shebang 

#!/usr/bin/env python

When is it better to use

#!/usr/bin/python

What is the exact difference between them?

Answer

vartec picture vartec · Apr 19, 2011

#!/usr/bin/python is hardcoded to always run /usr/bin/python, while #!/usr/bin/env python will run whichever python would be default in your current environment (it will take in account for example $PATH, you can check which python interpreter will be used with which python).

The second way ( #!/usr/bin/env python ) is preferred , as it's not dependent on particular installation. It will work for example with virtualenv setups or systems where there is no /usr/bin/python, but only e.g. /usr/local/bin/python.

Related questions

python subprocess Popen environment PATH?

I'm confused about how subprocess searches for the executable when using Popen(). It works if given absolute paths to the child process, but I'm trying to use relative paths. I've found that if I set the environment variable PYTHONPATH then …

Read More
Adding Anaconda to Path or not

The official recommendation is not to add Anaconda / Python to the Windows PATH environment variable. But how can I ensure then that my custom build scripts find python? (e.g. my sphinx make.bat).

Read More
How can I safely create a nested directory?

What is the most elegant way to check if the directory a file is going to be written to exists, and if not, create the directory using Python? Here is what I tried: import os file_path = "/my/directory/filename.…

Read More