Why do people write the #!/usr/bin/env python sheb

Question

It seems to me like the files run the same without that line.

Answer 1

If you're running your script in a virtual environment, say venv, then executing which python while working on venv will display the path to the Python interpreter:

~/Envs/venv/bin/python

Note that the name of the virtual environment is embedded in the path to the Python interpreter. Therefore, hardcoding this path in your script will cause two problems:

• If you upload the script to a repository, you're forcing other users to have the same virtual environment name. This is if they identify the problem first.
• You won't be able to run the script across multiple virtual environments even if you had all required packages in other virtual environments.

Therefore, to add to Jonathan's answer, the ideal shebang is #!/usr/bin/env python, not just for portability across OSes but for portability across virtual environments as well!