Как добавить python в path windows 10

4. Using Python on Windows¶

This document aims to give an overview of Windows-specific behaviour you should know about when using Python on Microsoft Windows.

Unlike most Unix systems and services, Windows does not include a system supported installation of Python. To make Python available, the CPython team has compiled Windows installers (MSI packages) with every release for many years. These installers are primarily intended to add a per-user installation of Python, with the core interpreter and library being used by a single user. The installer is also able to install for all users of a single machine, and a separate ZIP file is available for application-local distributions.

As specified in PEP 11, a Python release only supports a Windows platform while Microsoft considers the platform under extended support. This means that Python 3.10 supports Windows 8.1 and newer. If you require Windows 7 support, please install Python 3.8.

There are a number of different installers available for Windows, each with certain benefits and downsides.

The full installer contains all components and is the best option for developers using Python for any kind of project.

The Microsoft Store package is a simple installation of Python that is suitable for running scripts and packages, and using IDLE or other development environments. It requires Windows 10 and above, but can be safely installed without corrupting other programs. It also provides many convenient commands for launching Python and its tools.

The nuget.org packages are lightweight installations intended for continuous integration systems. It can be used to build Python packages or run scripts, but is not updateable and has no user interface tools.

The embeddable package is a minimal package of Python suitable for embedding into a larger application.

4.1. The full installer¶

4.1.1. Installation steps¶

Four Python 3.10 installers are available for download — two each for the 32-bit and 64-bit versions of the interpreter. The web installer is a small initial download, and it will automatically download the required components as necessary. The offline installer includes the components necessary for a default installation and only requires an internet connection for optional features. See Installing Without Downloading for other ways to avoid downloading during installation.

After starting the installer, one of two options may be selected:


If you select “Install Now”:

You will not need to be an administrator (unless a system update for the C Runtime Library is required or you install the Python Launcher for Windows for all users)

Python will be installed into your user directory

The Python Launcher for Windows will be installed according to the option at the bottom of the first page

The standard library, test suite, launcher and pip will be installed

If selected, the install directory will be added to your PATH

Shortcuts will only be visible for the current user

Selecting “Customize installation” will allow you to select the features to install, the installation location and other options or post-install actions. To install debugging symbols or binaries, you will need to use this option.

To perform an all-users installation, you should select “Customize installation”. In this case:

You may be required to provide administrative credentials or approval

Python will be installed into the Program Files directory

The Python Launcher for Windows will be installed into the Windows directory

Optional features may be selected during installation

The standard library can be pre-compiled to bytecode

If selected, the install directory will be added to the system PATH

Shortcuts are available for all users

4.1.2. Removing the MAX_PATH Limitation¶

Windows historically has limited path lengths to 260 characters. This meant that paths longer than this would not resolve and errors would result.

In the latest versions of Windows, this limitation can be expanded to approximately 32,000 characters. Your administrator will need to activate the “Enable Win32 long paths” group policy, or set LongPathsEnabled to 1 in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem .

This allows the open() function, the os module and most other path functionality to accept and return paths longer than 260 characters.

After changing the above option, no further configuration is required.

Changed in version 3.6: Support for long paths was enabled in Python.

4.1.3. Installing Without UI¶

All of the options available in the installer UI can also be specified from the command line, allowing scripted installers to replicate an installation on many machines without user interaction. These options may also be set without suppressing the UI in order to change some of the defaults.

To completely hide the installer UI and install Python silently, pass the /quiet option. To skip past the user interaction but still display progress and errors, pass the /passive option. The /uninstall option may be passed to immediately begin removing Python — no confirmation prompt will be displayed.

All other options are passed as name=value , where the value is usually 0 to disable a feature, 1 to enable a feature, or a path. The full list of available options is shown below.

Perform a system-wide installation.

The installation directory

Selected based on InstallAllUsers

The default installation directory for all-user installs

%ProgramFiles%\Python X.Y or %ProgramFiles(x86)%\Python X.Y

The default install directory for just-for-me installs

%LocalAppData%\Programs\PythonXY or %LocalAppData%\Programs\PythonXY-32 or %LocalAppData%\Programs\PythonXY-64

The default custom install directory displayed in the UI

Create file associations if the launcher is also installed.

Compile all .py files to .pyc .

Add install and Scripts directories to PATH and .PY to PATHEXT

Create shortcuts for the interpreter, documentation and IDLE if installed.

Install Python manual

Install debug binaries

Install developer headers and libraries. Omitting this may lead to an unusable installation.

Install python.exe and related files. Omitting this may lead to an unusable installation.

Installs the launcher for all users. Also requires Include_launcher to be set to 1

Install standard library and extension modules. Omitting this may lead to an unusable installation.

Install bundled pip and setuptools

Install debugging symbols ( * .pdb)

Install Tcl/Tk support and IDLE

Install standard library test suite

Install utility scripts

Only installs the launcher. This will override most other options.

Disable most install UI

A custom message to display when the simplified install UI is used.

For example, to silently install a default, system-wide Python installation, you could use the following command (from an elevated command prompt):

To allow users to easily install a personal copy of Python without the test suite, you could provide a shortcut with the following command. This will display a simplified initial page and disallow customization:

(Note that omitting the launcher also omits file associations, and is only recommended for per-user installs when there is also a system-wide installation that included the launcher.)

The options listed above can also be provided in a file named unattend.xml alongside the executable. This file specifies a list of options and values. When a value is provided as an attribute, it will be converted to a number if possible. Values provided as element text are always left as strings. This example file sets the same options as the previous example:

4.1.4. Installing Without Downloading¶

As some features of Python are not included in the initial installer download, selecting those features may require an internet connection. To avoid this need, all possible components may be downloaded on-demand to create a complete layout that will no longer require an internet connection regardless of the selected features. Note that this download may be bigger than required, but where a large number of installations are going to be performed it is very useful to have a locally cached copy.

Execute the following command from Command Prompt to download all possible required files. Remember to substitute python-3.9.0.exe for the actual name of your installer, and to create layouts in their own directories to avoid collisions between files with the same name.

You may also specify the /quiet option to hide the progress display.

4.1.5. Modifying an install¶

Once Python has been installed, you can add or remove features through the Programs and Features tool that is part of Windows. Select the Python entry and choose “Uninstall/Change” to open the installer in maintenance mode.

“Modify” allows you to add or remove features by modifying the checkboxes — unchanged checkboxes will not install or remove anything. Some options cannot be changed in this mode, such as the install directory; to modify these, you will need to remove and then reinstall Python completely.

“Repair” will verify all the files that should be installed using the current settings and replace any that have been removed or modified.

“Uninstall” will remove Python entirely, with the exception of the Python Launcher for Windows , which has its own entry in Programs and Features.

4.2. The Microsoft Store package¶

New in version 3.7.2.

The Microsoft Store package is an easily installable Python interpreter that is intended mainly for interactive use, for example, by students.

To install the package, ensure you have the latest Windows 10 updates and search the Microsoft Store app for “Python 3.10”. Ensure that the app you select is published by the Python Software Foundation, and install it.

Python will always be available for free on the Microsoft Store. If you are asked to pay for it, you have not selected the correct package.

After installation, Python may be launched by finding it in Start. Alternatively, it will be available from any Command Prompt or PowerShell session by typing python . Further, pip and IDLE may be used by typing pip or idle . IDLE can also be found in Start.

All three commands are also available with version number suffixes, for example, as python3.exe and python3.x.exe as well as python.exe (where 3.x is the specific version you want to launch, such as 3.10). Open “Manage App Execution Aliases” through Start to select which version of Python is associated with each command. It is recommended to make sure that pip and idle are consistent with whichever version of python is selected.

Virtual environments can be created with python -m venv and activated and used as normal.

If you have installed another version of Python and added it to your PATH variable, it will be available as python.exe rather than the one from the Microsoft Store. To access the new installation, use python3.exe or python3.x.exe .

The py.exe launcher will detect this Python installation, but will prefer installations from the traditional installer.

To remove Python, open Settings and use Apps and Features, or else find Python in Start and right-click to select Uninstall. Uninstalling will remove all packages you installed directly into this Python installation, but will not remove any virtual environments

4.2.1. Known issues¶ Redirection of local data, registry, and temporary paths¶

Because of restrictions on Microsoft Store apps, Python scripts may not have full write access to shared locations such as TEMP and the registry. Instead, it will write to a private copy. If your scripts must modify the shared locations, you will need to install the full installer.

At runtime, Python will use a private copy of well-known Windows folders and the registry. For example, if the environment variable %APPDATA% is c:\Users\<user>\AppData\ , then when writing to C:\Users\<user>\AppData\Local will write to C:\Users\<user>\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\Local\ .

When reading files, Windows will return the file from the private folder, or if that does not exist, the real Windows directory. For example reading C:\Windows\System32 returns the contents of C:\Windows\System32 plus the contents of C:\Program Files\WindowsApps\package_name\VFS\SystemX86 .

You can find the real path of any existing file using os.path.realpath() :

When writing to the Windows Registry, the following behaviors exist:

Reading from HKLM\\Software is allowed and results are merged with the registry.dat file in the package.

Writing to HKLM\\Software is not allowed if the corresponding key/value exists, i.e. modifying existing keys.

Writing to HKLM\\Software is allowed as long as a corresponding key/value does not exist in the package and the user has the correct access permissions.

For more detail on the technical basis for these limitations, please consult Microsoft’s documentation on packaged full-trust apps, currently available at docs.microsoft.com/en-us/windows/msix/desktop/desktop-to-uwp-behind-the-scenes

4.3. The nuget.org packages¶

New in version 3.5.2.

The nuget.org package is a reduced size Python environment intended for use on continuous integration and build systems that do not have a system-wide install of Python. While nuget is “the package manager for .NET”, it also works perfectly fine for packages containing build-time tools.

Visit nuget.org for the most up-to-date information on using nuget. What follows is a summary that is sufficient for Python developers.

The nuget.exe command line tool may be downloaded directly from https://aka.ms/nugetclidl , for example, using curl or PowerShell. With the tool, the latest version of Python for 64-bit or 32-bit machines is installed using:

To select a particular version, add a -Version 3.x.y . The output directory may be changed from . , and the package will be installed into a subdirectory. By default, the subdirectory is named the same as the package, and without the -ExcludeVersion option this name will include the specific version installed. Inside the subdirectory is a tools directory that contains the Python installation:

In general, nuget packages are not upgradeable, and newer versions should be installed side-by-side and referenced using the full path. Alternatively, delete the package directory manually and install it again. Many CI systems will do this automatically if they do not preserve files between builds.

Alongside the tools directory is a build\native directory. This contains a MSBuild properties file python.props that can be used in a C++ project to reference the Python install. Including the settings will automatically use the headers and import libraries in your build.

The package information pages on nuget.org are www.nuget.org/packages/python for the 64-bit version and www.nuget.org/packages/pythonx86 for the 32-bit version.

4.4. The embeddable package¶

New in version 3.5.

The embedded distribution is a ZIP file containing a minimal Python environment. It is intended for acting as part of another application, rather than being directly accessed by end-users.

When extracted, the embedded distribution is (almost) fully isolated from the user’s system, including environment variables, system registry settings, and installed packages. The standard library is included as pre-compiled and optimized .pyc files in a ZIP, and python3.dll , python37.dll , python.exe and pythonw.exe are all provided. Tcl/tk (including all dependants, such as Idle), pip and the Python documentation are not included.

The embedded distribution does not include the Microsoft C Runtime and it is the responsibility of the application installer to provide this. The runtime may have already been installed on a user’s system previously or automatically via Windows Update, and can be detected by finding ucrtbase.dll in the system directory.

Third-party packages should be installed by the application installer alongside the embedded distribution. Using pip to manage dependencies as for a regular Python installation is not supported with this distribution, though with some care it may be possible to include and use pip for automatic updates. In general, third-party packages should be treated as part of the application (“vendoring”) so that the developer can ensure compatibility with newer versions before providing updates to users.

The two recommended use cases for this distribution are described below.

4.4.1. Python Application¶

An application written in Python does not necessarily require users to be aware of that fact. The embedded distribution may be used in this case to include a private version of Python in an install package. Depending on how transparent it should be (or conversely, how professional it should appear), there are two options.

Using a specialized executable as a launcher requires some coding, but provides the most transparent experience for users. With a customized launcher, there are no obvious indications that the program is running on Python: icons can be customized, company and version information can be specified, and file associations behave properly. In most cases, a custom launcher should simply be able to call Py_Main with a hard-coded command line.

The simpler approach is to provide a batch file or generated shortcut that directly calls the python.exe or pythonw.exe with the required command-line arguments. In this case, the application will appear to be Python and not its actual name, and users may have trouble distinguishing it from other running Python processes or file associations.

With the latter approach, packages should be installed as directories alongside the Python executable to ensure they are available on the path. With the specialized launcher, packages can be located in other locations as there is an opportunity to specify the search path before launching the application.

4.4.2. Embedding Python¶

Applications written in native code often require some form of scripting language, and the embedded Python distribution can be used for this purpose. In general, the majority of the application is in native code, and some part will either invoke python.exe or directly use python3.dll . For either case, extracting the embedded distribution to a subdirectory of the application installation is sufficient to provide a loadable Python interpreter.

As with the application use, packages can be installed to any location as there is an opportunity to specify search paths before initializing the interpreter. Otherwise, there is no fundamental differences between using the embedded distribution and a regular installation.

4.5. Alternative bundles¶

Besides the standard CPython distribution, there are modified packages including additional functionality. The following is a list of popular versions and their key features:

Installer with multi-platform compatibility, documentation, PyWin32

Popular scientific modules (such as numpy, scipy and pandas) and the conda package manager.

“The Next Generation Python Environment and Package Manager”.

Previously Enthought provided Canopy, but it reached end of life in 2016.

Windows-specific distribution with prebuilt scientific packages and tools for building packages.

Note that these packages may not include the latest versions of Python or other libraries, and are not maintained or supported by the core Python team.

4.6. Configuring Python¶

To run Python conveniently from a command prompt, you might consider changing some default environment variables in Windows. While the installer provides an option to configure the PATH and PATHEXT variables for you, this is only reliable for a single, system-wide installation. If you regularly use multiple versions of Python, consider using the Python Launcher for Windows .

4.6.1. Excursus: Setting environment variables¶

Windows allows environment variables to be configured permanently at both the User level and the System level, or temporarily in a command prompt.

To temporarily set environment variables, open Command Prompt and use the set command:

These changes will apply to any further commands executed in that console, and will be inherited by any applications started from the console.

Including the variable name within percent signs will expand to the existing value, allowing you to add your new value at either the start or the end. Modifying PATH by adding the directory containing python.exe to the start is a common way to ensure the correct version of Python is launched.

To permanently modify the default environment variables, click Start and search for ‘edit environment variables’, or open System properties, Advanced system settings and click the Environment Variables button. In this dialog, you can add or modify User and System variables. To change System variables, you need non-restricted access to your machine (i.e. Administrator rights).

Windows will concatenate User variables after System variables, which may cause unexpected results when modifying PATH .

The PYTHONPATH variable is used by all versions of Python, so you should not permanently configure it unless the listed paths only include code that is compatible with all of your installed Python versions.

Overview of environment variables on Windows

The set command, for temporarily modifying environment variables

The setx command, for permanently modifying environment variables

4.6.2. Finding the Python executable¶

Changed in version 3.5.

Besides using the automatically created start menu entry for the Python interpreter, you might want to start Python in the command prompt. The installer has an option to set that up for you.

On the first page of the installer, an option labelled “Add Python to PATH” may be selected to have the installer add the install location into the PATH . The location of the Scripts\ folder is also added. This allows you to type python to run the interpreter, and pip for the package installer. Thus, you can also execute your scripts with command line options, see Command line documentation.

If you don’t enable this option at install time, you can always re-run the installer, select Modify, and enable it. Alternatively, you can manually modify the PATH using the directions in Excursus: Setting environment variables . You need to set your PATH environment variable to include the directory of your Python installation, delimited by a semicolon from other entries. An example variable could look like this (assuming the first two entries already existed):

4.7. UTF-8 mode¶

New in version 3.7.

Windows still uses legacy encodings for the system encoding (the ANSI Code Page). Python uses it for the default encoding of text files (e.g. locale.getpreferredencoding() ).

This may cause issues because UTF-8 is widely used on the internet and most Unix systems, including WSL (Windows Subsystem for Linux).

You can use the Python UTF-8 Mode to change the default text encoding to UTF-8. You can enable the Python UTF-8 Mode via the -X utf8 command line option, or the PYTHONUTF8=1 environment variable. See PYTHONUTF8 for enabling UTF-8 mode, and Excursus: Setting environment variables for how to modify environment variables.

When the Python UTF-8 Mode is enabled, you can still use the system encoding (the ANSI Code Page) via the “mbcs” codec.

Note that adding PYTHONUTF8=1 to the default environment variables will affect all Python 3.7+ applications on your system. If you have any Python 3.7+ applications which rely on the legacy system encoding, it is recommended to set the environment variable temporarily or use the -X utf8 command line option.

Even when UTF-8 mode is disabled, Python uses UTF-8 by default on Windows for:

Console I/O including standard I/O (see PEP 528 for details).

4.8. Python Launcher for Windows¶

New in version 3.3.

The Python launcher for Windows is a utility which aids in locating and executing of different Python versions. It allows scripts (or the command-line) to indicate a preference for a specific Python version, and will locate and execute that version.

Unlike the PATH variable, the launcher will correctly select the most appropriate version of Python. It will prefer per-user installations over system-wide ones, and orders by language version rather than using the most recently installed version.

The launcher was originally specified in PEP 397.

4.8.1. Getting started¶ From the command-line¶

Changed in version 3.6.

System-wide installations of Python 3.3 and later will put the launcher on your PATH . The launcher is compatible with all available versions of Python, so it does not matter which version is installed. To check that the launcher is available, execute the following command in Command Prompt:

You should find that the latest version of Python you have installed is started — it can be exited as normal, and any additional command-line arguments specified will be sent directly to Python.

If you have multiple versions of Python installed (e.g., 3.7 and 3.10) you will have noticed that Python 3.10 was started — to launch Python 3.7, try the command:

If you want the latest version of Python 2 you have installed, try the command:

You should find the latest version of Python 3.x starts.

If you see the following error, you do not have the launcher installed:

Per-user installations of Python do not add the launcher to PATH unless the option was selected on installation.

displays the currently installed version(s) of Python. Virtual environments¶

New in version 3.5.

If the launcher is run with no explicit Python version specification, and a virtual environment (created with the standard library venv module or the external virtualenv tool) active, the launcher will run the virtual environment’s interpreter rather than the global one. To run the global interpreter, either deactivate the virtual environment, or explicitly specify the global Python version. From a script¶

Let’s create a test Python script — create a file called hello.py with the following contents

From the directory in which hello.py lives, execute the command:

You should notice the version number of your latest Python 2.x installation is printed. Now try changing the first line to be:

Re-executing the command should now print the latest Python 3.x information. As with the above command-line examples, you can specify a more explicit version qualifier. Assuming you have Python 3.7 installed, try changing the first line to #! python3.7 and you should find the 3.10 version information printed.

Note that unlike interactive use, a bare “python” will use the latest version of Python 2.x that you have installed. This is for backward compatibility and for compatibility with Unix, where the command python typically refers to Python 2. From file associations¶

The launcher should have been associated with Python files (i.e. .py , .pyw , .pyc files) when it was installed. This means that when you double-click on one of these files from Windows explorer the launcher will be used, and therefore you can use the same facilities described above to have the script specify the version which should be used.

The key benefit of this is that a single launcher can support multiple Python versions at the same time depending on the contents of the first line.

4.8.2. Shebang Lines¶

If the first line of a script file starts with #! , it is known as a “shebang” line. Linux and other Unix like operating systems have native support for such lines and they are commonly used on such systems to indicate how a script should be executed. This launcher allows the same facilities to be used with Python scripts on Windows and the examples above demonstrate their use.

To allow shebang lines in Python scripts to be portable between Unix and Windows, this launcher supports a number of ‘virtual’ commands to specify which interpreter to use. The supported virtual commands are:

For example, if the first line of your script starts with

The default Python will be located and used. As many Python scripts written to work on Unix will already have this line, you should find these scripts can be used by the launcher without modification. If you are writing a new script on Windows which you hope will be useful on Unix, you should use one of the shebang lines starting with /usr .

Any of the above virtual commands can be suffixed with an explicit version (either just the major version, or the major and minor version). Furthermore the 32-bit version can be requested by adding “-32” after the minor version. I.e. /usr/bin/python3.7-32 will request usage of the 32-bit python 3.7.

New in version 3.7: Beginning with python launcher 3.7 it is possible to request 64-bit version by the “-64” suffix. Furthermore it is possible to specify a major and architecture without minor (i.e. /usr/bin/python3-64 ).

The /usr/bin/env form of shebang line has one further special property. Before looking for installed Python interpreters, this form will search the executable PATH for a Python executable. This corresponds to the behaviour of the Unix env program, which performs a PATH search.

4.8.3. Arguments in shebang lines¶

The shebang lines can also specify additional options to be passed to the Python interpreter. For example, if you have a shebang line:

Then Python will be started with the -v option

4.8.4. Customization¶ Customization via INI files¶

Two .ini files will be searched by the launcher — py.ini in the current user’s “application data” directory (i.e. the directory returned by calling the Windows function SHGetFolderPath with CSIDL_LOCAL_APPDATA ) and py.ini in the same directory as the launcher. The same .ini files are used for both the ‘console’ version of the launcher (i.e. py.exe) and for the ‘windows’ version (i.e. pyw.exe).

Customization specified in the “application directory” will have precedence over the one next to the executable, so a user, who may not have write access to the .ini file next to the launcher, can override commands in that global .ini file. Customizing default Python versions¶

In some cases, a version qualifier can be included in a command to dictate which version of Python will be used by the command. A version qualifier starts with a major version number and can optionally be followed by a period (‘.’) and a minor version specifier. Furthermore it is possible to specify if a 32 or 64 bit implementation shall be requested by adding “-32” or “-64”.

For example, a shebang line of #!python has no version qualifier, while #!python3 has a version qualifier which specifies only a major version.

If no version qualifiers are found in a command, the environment variable PY_PYTHON can be set to specify the default version qualifier. If it is not set, the default is “3”. The variable can specify any value that may be passed on the command line, such as “3”, “3.7”, “3.7-32” or “3.7-64”. (Note that the “-64” option is only available with the launcher included with Python 3.7 or newer.)

If no minor version qualifiers are found, the environment variable PY_PYTHON (where is the current major version qualifier as determined above) can be set to specify the full version. If no such option is found, the launcher will enumerate the installed Python versions and use the latest minor release found for the major version, which is likely, although not guaranteed, to be the most recently installed version in that family.

On 64-bit Windows with both 32-bit and 64-bit implementations of the same (major.minor) Python version installed, the 64-bit version will always be preferred. This will be true for both 32-bit and 64-bit implementations of the launcher — a 32-bit launcher will prefer to execute a 64-bit Python installation of the specified version if available. This is so the behavior of the launcher can be predicted knowing only what versions are installed on the PC and without regard to the order in which they were installed (i.e., without knowing whether a 32 or 64-bit version of Python and corresponding launcher was installed last). As noted above, an optional “-32” or “-64” suffix can be used on a version specifier to change this behaviour.

If no relevant options are set, the commands python and python2 will use the latest Python 2.x version installed and the command python3 will use the latest Python 3.x installed.

The command python3.7 will not consult any options at all as the versions are fully specified.

If PY_PYTHON=3 , the commands python and python3 will both use the latest installed Python 3 version.

If PY_PYTHON=3.7-32 , the command python will use the 32-bit implementation of 3.7 whereas the command python3 will use the latest installed Python (PY_PYTHON was not considered at all as a major version was specified.)

If PY_PYTHON=3 and PY_PYTHON3=3.7 , the commands python and python3 will both use specifically 3.7

In addition to environment variables, the same settings can be configured in the .INI file used by the launcher. The section in the INI file is called [defaults] and the key name will be the same as the environment variables without the leading PY_ prefix (and note that the key names in the INI file are case insensitive.) The contents of an environment variable will override things specified in the INI file.

Setting PY_PYTHON=3.7 is equivalent to the INI file containing:

Setting PY_PYTHON=3 and PY_PYTHON3=3.7 is equivalent to the INI file containing:

4.8.5. Diagnostics¶

If an environment variable PYLAUNCH_DEBUG is set (to any value), the launcher will print diagnostic information to stderr (i.e. to the console). While this information manages to be simultaneously verbose and terse, it should allow you to see what versions of Python were located, why a particular version was chosen and the exact command-line used to execute the target Python.

4.9. Finding modules¶

Python usually stores its library (and thereby your site-packages folder) in the installation directory. So, if you had installed Python to C:\Python\ , the default library would reside in C:\Python\Lib\ and third-party modules should be stored in C:\Python\Lib\site-packages\ .

To completely override sys.path , create a ._pth file with the same name as the DLL ( python37._pth ) or the executable ( python._pth ) and specify one line for each path to add to sys.path . The file based on the DLL name overrides the one based on the executable, which allows paths to be restricted for any program loading the runtime if desired.

When the file exists, all registry and environment variables are ignored, isolated mode is enabled, and site is not imported unless one line in the file specifies import site . Blank paths and lines starting with # are ignored. Each path may be absolute or relative to the location of the file. Import statements other than to site are not permitted, and arbitrary code cannot be specified.

Note that .pth files (without leading underscore) will be processed normally by the site module when import site has been specified.

When no ._pth file is found, this is how sys.path is populated on Windows:

An empty entry is added at the start, which corresponds to the current directory.

If the environment variable PYTHONPATH exists, as described in Environment variables , its entries are added next. Note that on Windows, paths in this variable must be separated by semicolons, to distinguish them from the colon used in drive identifiers ( C:\ etc.).

Additional “application paths” can be added in the registry as subkeys of \SOFTWARE\Python\PythonCore\PythonPath under both the HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE hives. Subkeys which have semicolon-delimited path strings as their default value will cause each path to be added to sys.path . (Note that all known installers only use HKLM, so HKCU is typically empty.)

If the environment variable PYTHONHOME is set, it is assumed as “Python Home”. Otherwise, the path of the main Python executable is used to locate a “landmark file” (either Lib\os.py or pythonXY.zip ) to deduce the “Python Home”. If a Python home is found, the relevant sub-directories added to sys.path ( Lib , plat-win , etc) are based on that folder. Otherwise, the core Python path is constructed from the PythonPath stored in the registry.

If the Python Home cannot be located, no PYTHONPATH is specified in the environment, and no registry entries can be found, a default path with relative entries is used (e.g. .\Lib;.\plat-win , etc).

If a pyvenv.cfg file is found alongside the main executable or in the directory one level above the executable, the following variations apply:

If home is an absolute path and PYTHONHOME is not set, this path is used instead of the path to the main executable when deducing the home location.

The end result of all this is:

When running python.exe , or any other .exe in the main Python directory (either an installed version, or directly from the PCbuild directory), the core path is deduced, and the core paths in the registry are ignored. Other “application paths” in the registry are always read.

When Python is hosted in another .exe (different directory, embedded via COM, etc), the “Python Home” will not be deduced, so the core path from the registry is used. Other “application paths” in the registry are always read.

If Python can’t find its home and there are no registry value (frozen .exe, some very strange installation setup) you get a path with some default, but relative, paths.

For those who want to bundle Python into their application or distribution, the following advice will prevent conflicts with other installations:

Include a ._pth file alongside your executable containing the directories to include. This will ignore paths listed in the registry and environment variables, and also ignore site unless import site is listed.

If you are loading python3.dll or python37.dll in your own executable, explicitly call Py_SetPath() or (at least) Py_SetProgramName() before Py_Initialize() .

Clear and/or overwrite PYTHONPATH and set PYTHONHOME before launching python.exe from your application.

If you cannot use the previous suggestions (for example, you are a distribution that allows people to run python.exe directly), ensure that the landmark file ( Lib\os.py ) exists in your install directory. (Note that it will not be detected inside a ZIP file, but a correctly named ZIP file will be detected instead.)

These will ensure that the files in a system-wide installation will not take precedence over the copy of the standard library bundled with your application. Otherwise, your users may experience problems using your application. Note that the first suggestion is the best, as the others may still be susceptible to non-standard paths in the registry and user site-packages.

  • Adds ._pth file support and removes applocal option from pyvenv.cfg .

  • Adds pythonXX.zip as a potential landmark when directly adjacent to the executable.

Deprecated since version 3.6:

Modules specified in the registry under Modules (not PythonPath ) may be imported by importlib.machinery.WindowsRegistryFinder . This finder is enabled on Windows in 3.6.0 and earlier, but may need to be explicitly added to sys.meta_path in the future.

4.10. Additional modules¶

Even though Python aims to be portable among all platforms, there are features that are unique to Windows. A couple of modules, both in the standard library and external, and snippets exist to use these features.

The Windows-specific standard modules are documented in MS Windows Specific Services .

4.10.1. PyWin32¶

The PyWin32 module by Mark Hammond is a collection of modules for advanced Windows-specific support. This includes utilities for:

Win32 API calls

PythonWin is a sample MFC application shipped with PyWin32. It is an embeddable IDE with a built-in debugger.

by David and Paul Boddie

4.10.2. cx_Freeze¶

cx_Freeze is a distutils extension (see Extending Distutils ) which wraps Python scripts into executable Windows programs ( * .exe files). When you have done this, you can distribute your application without requiring your users to install Python.

4.11. Compiling Python on Windows¶

If you want to compile CPython yourself, first thing you should do is get the source. You can download either the latest release’s source or just grab a fresh checkout.

The source tree contains a build solution and project files for Microsoft Visual Studio, which is the compiler used to build the official Python releases. These files are in the PCbuild directory.

Check PCbuild/readme.txt for general information on the build process.

4.12. Other Platforms¶

With ongoing development of Python, some platforms that used to be supported earlier are no longer supported (due to the lack of users or developers). Check PEP 11 for details on all unsupported platforms.

Windows CE is no longer supported since Python 3 (if it ever was).

The Cygwin installer offers to install the Python interpreter as well

See Python for Windows for detailed information about platforms with pre-compiled installers.

Adding Python to PATH on Windows

I’ve been trying to add the Python path to the command line on Windows, yet no matter the method I try, nothing seems to work. I’ve used the set command, I’ve tried adding it through the Edit Environment Variables prompt, etc.

Furthermore, if I run the set command on the command line it lists this.

Yet it still doesn’t recognize the Python command.

Reading the documentation, and various other sources haven’t seemed to help.

Just to clarify further, I’ve appended the path of the Python executable to PATH in the Edit Environment prompt. Doesn’t seem to work.


22 Answers 22

  1. Hold Win and press Pause .
  2. Click Advanced System Settings.
  3. Click Environment Variables.
  4. Append ;C:\python27 to the Path variable.
  5. Restart Command Prompt.


When setting Environmental Variables in Windows, I have gone wrong on many, many occasions. I thought I should share a few of my past mistakes here hoping that it might help someone. (These apply to all Environmental Variables, not just when setting Python Path)

Watch out for these possible mistakes:

  1. Kill and reopen your shell window: Once you make a change to the ENVIRONMENTAL Variables, you have to restart the window you are testing it on.
  2. NO SPACES when setting the Variables. Make sure that you are adding the ;C:\Python27 WITHOUT any spaces. (It is common to try C:\SomeOther; C:\Python27 That space (␣) after the semicolon is not okay.)
  3. USE A BACKWARD SLASH when spelling out your full path. You will see forward slashes when you try echo $PATH but only backward slashes have worked for me.
  4. DO NOT ADD a final backslash. Only C:\Python27 NOT C:\Python27\

Hope this helps someone.

Open cmd.exe with administrator privileges (right click on app). Then type:

Remember to end with a semi-colon and don’t include a trailing slash.


I’ve had a problem with this for a LONG time. I added it to my path in every way I could think of but here’s what finally worked for me:

  1. Right click on «My computer»
  2. Click «Properties»
  3. Click «Advanced system settings» in the side panel
  4. Click «Environment Variables»
  5. Click the «New» below system variables
  6. in name enter pythonexe (or anything you want)
  7. in value enter the path to your python (example: C:\Python32\ )
  8. Now edit the Path variable (in the system part) and add %pythonexe%; to the end of what’s already there

IDK why this works but it did for me.

then try typing «python» into your command line and it should work!

Lately I’ve been using this program which seems to work pretty well. There’s also this one which looks pretty good too, although I’ve never tried it.

Try adding this python.bat file to System32 folder and the command line will now run python when you type in python


You can set the path from the current cmd window using the PATH = command. That will only add it for the current cmd instance. if you want to add it permanently, you should add it to system variables. (Computer > Advanced System Settings > Environment Variables)

You would goto your cmd instance, and put in PATH=C:/Python27/;%PATH% .

Jean-François Fabre

Make sure you don’t add a space before the new directory.

Bad: old;old;old; new

The following program will add the python executable path and the subdir Scripts (which is where e.g. pip and easy_install are installed) to your environment. It finds the path to the python executable from the registry key binding the .py extension. It will remove old python paths in your environment. Works with XP (and probably Vista) as well. It only uses modules that come with the basic windows installer.

Python comes with a small utility that does just this. From the command line run:

Make sure you close the command window (with exit or the close button) and open it again.

I know this post is old but I’d like to add that the solutions assume admin privs. If you don’t have those you can:

Go to control panel, type path (this is Windows 7 now so that’s in the Search box) and click «Edit Environment variables for your account». You’ll now see the Environment Variable dialog with «User variables» on the top and «System variables» below.

You can, as a user, click the top «New» button and add:

Variable name: PATH
Variable value: C:\Python27

(no spaces anywhere) and click OK. Once your command prompt is restarted, any PATH in the User variables is appended to the end of the System Path. It doesn’t replace the PATH in any other way.

If you want a specific full path set up, you’re better off creating a batch file like this little one:

Как добавить Python в переменную PATH Windows

Часто работает Питон Из Терминала это неизбежно. Однако, если вы впервые установили Python в Windows 10, запуск его через Терминал Windows возможен только в том случае, если он добавлен в переменную среды Windows PATH.

Это может показаться трудным, но бояться нечего. Чтобы помочь вам пройти через все взлеты и падения, связанные с добавлением Python в ваш Windows PATH после его установки, давайте рассмотрим несколько задействованных вариантов и шагов.

Зачем добавлять Python в PATH Windows?

Если вам не удалось добавить Python в PATH в вашей Windows, вы не сможете запустить компилятор Python, запустить виртуальную среду программирования или выполнить такие команды, как пип установить от Терминала.

Это связано с тем, что, когда вы запускаете любое приложение, отличное от заданного по умолчанию, из командной строки, Терминал ищет исполняемый файл в текущей папке или по пути Windows.

Если его нет в переменной PATH, Терминал возвращает ошибку «Не существует«. Добавление в PATH — это мощная команда, поэтому, даже если вы выполняете команду из сгенерированного или пакетного файла по умолчанию, добавление ее основного исполняемого файла в переменную PATH также делает ее вызываемой из Терминала.

Как вручную добавить Python в Windows PATH

Во-первых, если на вашем устройстве не установлен Python, перейдите на сайт python.org Загрузите и установите желаемую версию.

После успешной установки Python на ваш компьютер проверьте, не был ли он уже добавлен в PATH Windows. Откройте Терминал и введите питон , затем нажмите клавишу. Enter. Команда может отображать сообщение об ошибке «‘python’ не распознается как внутренняя или внешняя команда, работающая программа или командный файл», Указывая на то, что Python еще не добавлен в переменную PATH вашего устройства.

Чтобы запускать программы Python из командной строки, выполните следующие действия.

Найдите путь установки Python на вашем компьютере

Чтобы добавить Python в PATH Windows, вам необходимо получить путь его установки. Для этого откройте панель поиска Windows и введите python.exe (не нажимайте клавишу Enter). Затем щелкните правой кнопкой мыши Python.exe, который появляется в появившемся меню, и выберите вариант. местонахождение открытого файла.

В открывшемся окне проводника щелкните длинную панель каталогов слева от строки поиска. Выделите весь текст пути и скопируйте его в буфер обмена с помощью Ctrl + C. Затем перейдите к следующим шагам ниже.

Добавление Python в PATH в пользовательских переменных

Чтобы добавить Python в PATH в пользовательских переменных, щелкните правой кнопкой мыши «Этот компьютер» и выберите ئصائص. Оказавшись в меню свойств, нажмите на опцию Расширенные системные настройки. В следующем окне выберите вкладку Расширенные настройки , и выберите переменные среды.

Список переменных среды состоит из двух отдельных частей: верхней части, называемой пользовательскими переменными, и нижней части, называемой системными переменными. Однако в этом случае мы сосредоточимся на пользовательских переменных.

в списке Пользовательские переменные найдите переменную с именем. Path. Затем вставьте путь, который вы скопировали ранее, в параметр значения переменной, используя Ctrl + V И нажмите Ok.

Однако, если вы не можете найти эту переменную, вам может потребоваться ее создать. Для этого нажмите Новое. Затем в форме имени переменной введите Path и вставьте путь Python в поле значения переменной.

Вернитесь в папку пути установки Python и дважды щелкните Сценарии чтобы открыть этот каталог. Затем скопируйте его путь из панели пути в верхней части окна (рядом с панелью поиска), как вы это делали ранее с путем установки Python.

Как только вы скопируете трек Сценарии , вернитесь к переменным среды. Затем выберите переменную Path и щелкните «Изменить». Введите точку с запятой после пути к исполняемому файлу Python и вставьте путь Сценарии который вы только что скопировали после. Затем нажмите Ok.

Добавление Python в PATH с опцией системных переменных

Вы также можете добавить Python в системные переменные PATH. Хотя это всего лишь альтернатива, и в ней нет необходимости, если вы уже добавили ее в пользовательские переменные.

Чтобы использовать параметр «Системные переменные», выполните описанные выше действия, чтобы скопировать путь Python и его путь к сценариям. Затем вернитесь к переменным среды. Затем в разделе «Системные переменные» найдите переменную с именем Path. Щелкните эту переменную и щелкните Выпуск.

В следующем появившемся окне нажмите New и вставьте путь, который вы скопировали ранее, в открытое пространство. Повторите этот процесс также для пути скриптов. Далее коснитесь Ok И закройте окно переменных среды.

Добавить Python в Windows PATH автоматически

Вы также можете автоматически добавить Python в свой Windows PATH во время установки. Хотя этот метод работает не во всех случаях, вы все же можете попробовать.

Для этого щелкните свой установочный файл и установите флажок «Добавить Python 3.7 в PATH». Номер версии изменится при установке разных версий Python.

Установка этого флажка автоматически добавит Python в ПУТЬ Windows. Это означает, что вы можете запускать команды Python через командную строку сразу после установки.

Убедитесь, что вы добавили Python в свой путь к Windows.

Чтобы узнать, был ли Python уже добавлен в Windows PATH, откройте Терминал и введите python — version, затем нажмите клавишу Enter. Если команда возвращает текущую установленную версию Python, это означает, что вы успешно добавили ее в свой путь Windows.

Однако, чтобы проверить, добавили ли вы путь к сценариям в Windows PATH, попробуйте выполнить команду пакет установки pip в Терминале и замените «пакет» своей любимой библиотекой. Если вы установили Python 2.7.9 и новее, команда устанавливает указанный пакет, указывая, что вы также успешно добавили скрипты Python в путь.

Еще одно приложение, о котором вам следует подумать о добавлении в ваш путь к Windows.

Помимо добавления Python в ваш Windows PATH, вы можете добавить приложения для редактирования текста, интегрированные среды разработки (IDE), Git, Node, Anaconda и многие другие.

Например, управлять проектами с помощью Sublime Text легко, когда вы открываете Терминал в каталоге папки проекта и запускаете команду subl.. Это откроет отредактированную команду в вашей текущей папке и отобразит ее на боковой панели, еще один экономящий время ярлык для продуктивной работы. Sublime Text.

How to add Python to Windows PATH

There are few ways to add Python to Windows PATH. In this guide, you’ll see two methods to add Python to Windows path:

  • Via the installation of a recent version of Python
  • Manual entry of the paths

Method 1: Install a Recent Version of Python

You can easily add Python to Windows path by downloading a recent version of Python, and then checking the box to Add Python to PATH at the bottom of the setup screen:

Add Python to PATH

Finish the installation, and you should be good to go.

Alternatively, you may manually add the paths into the Environment variables.

Method 2: Manually add Python to Windows Path

If you wish to stick with the previous version of Python, you may apply the steps below to manually add Python to Windows path.

First, navigate to the Windows Environment Variables screen (where you can add/edit your paths):

  • Press the Windows Key + R on your keyboard in order to open the Run dialog box
  • Type sysdm.cpl to open the System Properties
  • Go to the Advanced tab and then click on the ‘Environment Variables…

That should take you to the Environment Variables screen, where you can add/edit your paths.

Under the User variables box, click on ‘New…‘ to add the ‘Path’ variable (note that if your ‘Path’ variable already exists, then click on ‘Edit…’ instead):

New… Edit…

You should then see the New User Variable box, where you may add/edit variables:

Before you type any values, you’ll need to locate the relevant Python paths. The paths that you’ll need to get are:

(1) The Python application path, which is the folder where you originally installed Python. You can find the Python application path by following these steps:

  • Type “Python” in the Windows Search Bar
  • Right-click on the Python App, and then select “Open file location
  • Right-click again on the Python shortcut, and then select “Open file location

Here is an example of a Python application path:

(2) The Python Scripts path. The Scripts folder should be located within the Python application path. Example:

After you obtained the paths, fill the New User Variable box that you saw earlier:

  • For the Variable name, type ‘Path
  • For the Variable value, copy the full Python application path, then use semicolon (as highlighted in yellow below), and finally copy the Python Scripts path.

For our example:

Press ‘OK’ and you would then see your new Python Path under the ‘User variables‘ section. Don’t forget to press ‘OK‘ again so that the changes will get implemented.

OK Cancel

You just added Python to the Windows Path.

You should be able to install Python packages easily, by opening the Windows Command Prompt and then typing:

For example, to install the Pandas package, simply type ‘pip install pandas‘ and then press ENTER:

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *