nuget.exe install python -ExcludeVersion -OutputDirectory . nuget.exe install pythonx86 -ExcludeVersion -OutputDirectory . 

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: 

# Without -ExcludeVersion > .\python.3.5.2	ools\python.exe -V Python 3.5.2 # With -ExcludeVersion > .\python	ools\python.exe -V Python 3.5.2 

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
ative 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. 

## 3.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. 

Note: 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. 

