Python: Setting up the environment
2026-02-21 23:40 Diff
https://hexlet.io/courses/python-setup-environment/lessons/python-scripts/theory_unit

There is only one step from writing code to running it in interpreted languages. We do not need to compile anything into machine code.

The interpreter does all the work. It only needs to input a script — a program in an interpreted language. Within this program, we have simple sequences of commands that the computer needs to execute.

If's is convenient to write scripts in a language, it gets called a scripting language.

Python scripts

Python is an excellent scripting language. We do not have to formalize the sequence of commands in simple scripts. We run the scripts as simply as possible and write the commands one by one into the file:

Then we call the interpreter with the received file as input:

Python has many modules and functions included. Therefore, we often use them to automate tasks we don't want to perform manually. In addition, scripting is a great starting point for those who begin to get acquainted with programming.

Scripts and shebang

In Linux, macOS, BSD, and other UNIX-like operating systems, shells can run scripts in any language, including Python.

The scripts tell the shell which interpreter to call to execute the script. We specify the interpreter by shebang — a string in the very first line of the script file. This name comes from the first two characters of such a string: # is called sharp, and ! — bang.

A typical shebang looks like this:

After the #! characters comes the path to the interpreter. When you run a script with shebang, the shell reads the first line and tries to run the specified interpreter.

If we give execution rights to a script with the specified shebang, we can omit the interpreter on the command line:

Shebang and different versions of Python

Shebang usually is pretty simple when there's only one interpreter in the system. But there can be several versions of Python installed on a system. Moreover, the path to the interpreter in a virtual environment will be different from /usr/bin and other environments.

How do I make the script always run with the correct version of Python? You can use the env program instead of specifying the path to the python command directly.

This program finds and runs programs to environment variables. When the virtual environment is activated, the $PATH variable is modified so that env will run the exact version of the interpreter needed. The interpreter will find the correct version earlier because we added the path to the environment binaries at the beginning of $PATH.

Now let us look at the correct way to specify shebang in Python projects:

We always give the path to env, because this program is almost always located there and won't appear in several versions.