Why don't I add Python.exe to my system path during installation?

I am reinstalling Python on Windows 7, and one of the first dialogs is the Configure Python screen.

By default, the option "Add Python.exe to the path" is set to "All function will be unavailable."

I always change this to "Will be installed on the local hard drive."

This is not a problem; changing system environment variables is a binding, but is there any potential for leaving this unchecked?

+6
source share
2 answers

If you have only one version of Python installed, that doesn't matter.

If you have several versions installed, the first one that appears on your Path system will be executed when you use the python command. In addition, it can make older versions inaccessible without additional work. For example, I had a system with Python 2.7 installed, and I added 3.2 on top of it and checked the ability to add Python.exe to the path during installation. After that, input into "python" and "python3" at the command line opened Python 3.2, so I would need to enter the full path to the interpreter 2.7 when I needed to execute 2.x scripts.

+7
source

One potential I can think of is running multiple versions of python on Windows. So, you have c: \ python34 and c: \ python27 , but both are on the way, you will get what comes sooner, which will lead to an unexpected result.

+1
source

Source: https://habr.com/ru/post/972334/


All Articles