4. 윈도우에서 파이썬 사용하기¶

이 문서는 Microsoft 윈도우에서 파이썬을 사용할 때 알아야 할 윈도우 특정 동작에 대한 개요를 제공하는 것을 목표로 합니다.

Unlike most Unix systems and services, Windows does not include a system supported installation of Python. Instead, Python can be obtained from a number of distributors, including directly from the CPython team. Each Python distribution will have its own benefits and drawbacks, however, consistency with other tools you are using is generally a worthwhile benefit. Before committing to the process described here, we recommend investigating your existing tools to see if they can provide Python directly.

To obtain Python from the CPython team, use the Python Install Manager. This is a standalone tool that makes Python available as global commands on your Windows machine, integrates with the system, and supports updates over time. You can download the Python Install Manager from python.org/downloads or through the Microsoft Store app.

Once you have installed the Python Install Manager, the global python command can be used from any terminal to launch your current latest version of Python. This version may change over time as you add or remove different versions, and the py list command will show which is current.

In general, we recommend that you create a virtual environment for each project and run <env>\Scripts\Activate in your terminal to use it. This provides isolation between projects, consistency over time, and ensures that additional commands added by packages are also available in your session. Create a virtual environment using python -m venv <env path>.

If the python or py commands do not seem to be working, please see the Troubleshooting section below. There are sometimes additional manual steps required to configure your PC.

Apart from using the Python install manager, Python can also be obtained as NuGet packages. See nuget.org 패키지 below for more information on these packages.

The embeddable distros are minimal packages of Python suitable for embedding into larger applications. They can be installed using the Python install manager. See 내장 가능한 패키지 below for more information on these packages.

4.1. Python install manager¶

4.1.1. Installation¶

The Python install manager can be installed from the Microsoft Store app or downloaded and installed from python.org/downloads. The two versions are identical.

To install through the Store, simply click “Install”. After it has completed, open a terminal and type python to get started.

To install the file downloaded from python.org, either double-click and select “Install”, or run Add-AppxPackage <path to MSIX> in Windows Powershell.

After installation, the python, py, and pymanager commands should be available. If you have existing installations of Python, or you have modified your PATH variable, you may need to remove them or undo the modifications. See Troubleshooting for more help with fixing non-working commands.

When you first install a runtime, you will likely be prompted to add a directory to your PATH. This is optional, if you prefer to use the py command, but is offered for those who prefer the full range of aliases (such as python3.14.exe) to be available. The directory will be %LocalAppData%\Python\bin by default, but may be customized by an administrator. Click Start and search for “Edit environment variables for your account” for the system settings page to add the path.

Each Python runtime you install will have its own directory for scripts. These also need to be added to PATH if you want to use them.

The Python install manager will be automatically updated to new releases. This does not affect any installs of Python runtimes. Uninstalling the Python install manager does not uninstall any Python runtimes.

If you are not able to install an MSIX in your context, for example, you are using automated deployment software that does not support it, or are targeting Windows Server 2019, please see Advanced installation below for more information.

4.1.2. Basic use¶

The recommended command for launching Python is python, which will either launch the version requested by the script being launched, an active virtual environment, or the default installed version, which will be the latest stable release unless configured otherwise. If no version is specifically requested and no runtimes are installed at all, the current latest release will be installed automatically.

For all scenarios involving multiple runtime versions, the recommended command is py. This may be used anywhere in place of python or the older py.exe launcher. By default, py matches the behaviour of python, but also allows command line options to select a specific version as well as subcommands to manage installations. These are detailed below.

Because the py command may already be taken by the previous version, there is also an unambiguous pymanager command. Scripted installs that are intending to use Python install manager should consider using pymanager, due to the lower chance of encountering a conflict with existing installs. The only difference between the two commands is when running without any arguments: py will launch your default interpreter, while pymanager will display help (pymanager exec ... provides equivalent behaviour to py ...).

Each of these commands also has a windowed version that avoids creating a console window. These are pyw, pythonw and pywmanager. A python3 command is also included that mimics the python command. It is intended to catch accidental uses of the typical POSIX command on Windows, but is not meant to be widely used or recommended.

To launch your default runtime, run python or py with the arguments you want to be passed to the runtime (such as script files or the module to launch):

$> py
...
$> python my-script.py
...
$> py -m this
...

The default runtime can be overridden with the PYTHON_MANAGER_DEFAULT environment variable, or a configuration file. See Configuration for information about configuration settings.

To launch a specific runtime, the py command accepts a -V:<TAG> option. This option must be specified before any others. The tag is part or all of the identifier for the runtime; for those from the CPython team, it looks like the version, potentially with the platform. For compatibility, the V: may be omitted in cases where the tag refers to an official release and starts with 3.

$> py -V:3.14 ...
$> py -V:3-arm64 ...

Runtimes from other distributors may require the company to be included as well. It should be separated from the tag by a slash (either / or \), and may be shortened to any prefix of its full value. Specifying the company is optional when it is PythonCore, and specifying the tag is optional (but not the slash) when you want the latest release from a specific company.

$> py -V:Distributor\1.0 ...
$> py -V:distrib/ ...

If no version is specified, but a script file is passed, the script will be inspected for a shebang line. This is a special format for the first line in a file that allows overriding the command. See Shebang lines for more information. When there is no shebang line, or it cannot be resolved, the script will be launched with the default runtime.

If you are running in an active virtual environment, have not requested a particular version, and there is no shebang line, the default runtime will be that virtual environment. In this scenario, the python command was likely already overridden and none of these checks occurred. However, this behaviour ensures that the py command can be used interchangeably.

When no runtimes are installed, any launch command will try to install the requested version and launch it. However, after any version is installed, only the py exec ... and pymanager exec ... commands will install if the requested version is absent. Other forms of commands will display an error and direct you to use py install first.

4.1.3. Command help¶

The py help command will display the full list of supported commands, along with their options. Any command may be passed the -? option to display its help, or its name passed to py help.

$> py help
$> py help install
$> py install /?

All commands support some common options, which will be shown by py help. These options must be specified after any subcommand. Specifying -v or --verbose will increase the amount of output shown, and -vv will increase it further for debugging purposes. Passing -q or --quiet will reduce output, and -qq will reduce it further.

The --config=<PATH> option allows specifying a configuration file to override multiple settings at once. See Configuration below for more information about these files.

4.1.4. Listing runtimes¶

$> py list [-f=|--format=<FMT>] [-1|--one] [--online|-s=|--source=<URL>] [<TAG>...]

The list of installed runtimes can be seen using py list. A filter may be added in the form of one or more tags (with or without company specifier), and each may include a <, <=, >= or > prefix to restrict to a range.

A range of formats are supported, and can be passed as the --format=<FMT> or -f <FMT> option. Formats include table (a user friendly table view), csv (comma-separated table), json (a single JSON blob), jsonl (one JSON blob per result), exe (just the executable path), prefix (just the prefix path).

The --one or -1 option only displays a single result. If the default runtime is included, it will be the one. Otherwise, the “best” result is shown (“best” is deliberately vaguely defined, but will usually be the most recent version). The result shown by py list --one <TAG> will match the runtime that would be launched by py -V:<TAG>.

The --only-managed option excludes results that were not installed by the Python install manager. This is useful when determining which runtimes may be updated or uninstalled through the py command.

The --online option is short for passing --source=<URL> with the default source. Passing either of these options will search the online index for runtimes that can be installed. The result shown by py list --online --one <TAG> will match the runtime that would be installed by py install <TAG>.

$> py list --online 3.14

For compatibility with the old launcher, the --list, --list-paths, -0 and -0p commands (e.g. py -0p) are retained. They do not allow additional options, and will produce legacy formatted output.

4.1.5. Installing runtimes¶

$> py install [-s=|--source=<URL>] [-f|--force] [-u|--update] [--dry-run] [<TAG>...]

New runtime versions may be added using py install. One or more tags may be specified, and the special tag default may be used to select the default. Ranges are not supported for installation.

The --source=<URL> option allows overriding the online index that is used to obtain runtimes. This may be used with an offline index, as shown in Offline installs.

Passing --force will ignore any cached files and remove any existing install to replace it with the specified one.

Passing --update will replace existing installs if the new version is newer. Otherwise, they will be left. If no tags are provided with --update, all installs managed by the Python install manager will be updated if newer versions are available. Updates will remove any modifications made to the install, including globally installed packages, but virtual environments will continue to work.

Passing --dry-run will generate output and logs, but will not modify any installs.

Passing --refresh will update all registrations for installed runtimes. This will recreate Start menu shortcuts, registry keys, and global aliases (such as python3.14.exe or for any installed scripts). These are automatically refreshed on installation of any runtime, but may need to be manually refreshed after installing packages.

In addition to the above options, the --target option will extract the runtime to the specified directory instead of doing a normal install. This is useful for embedding runtimes into larger applications. Unlike a normal install, py will not be aware of the extracted runtime, and no Start menu or other shortcuts will be created. To launch the runtime, directly execute the main executable (typically python.exe) in the target directory.

$> py install ... [-t=|--target=<PATH>] <TAG>

The py exec command will install the requested runtime if it is not already present. This is controlled by the automatic_install configuration (PYTHON_MANAGER_AUTOMATIC_INSTALL), and is enabled by default. If no runtimes are available at all, all launch commands will do an automatic install if the configuration setting allows. This is to ensure a good experience for new users, but should not generally be relied on rather than using the py exec command or explicit install commands.

4.1.6. Offline installs¶

To perform offline installs of Python, you will need to first create an offline index on a machine that has network access.

$> py install --download=<PATH> ... <TAG>...

The --download=<PATH> option will download the packages for the listed tags and create a directory containing them and an index.json file suitable for later installation. This entire directory can be moved to the offline machine and used to install one or more of the bundled runtimes:

$> py install --source="<PATH>\index.json" <TAG>...

The Python install manager can be installed by downloading its installer and moving it to another machine before installing.

Alternatively, the ZIP files in an offline index directory can simply be transferred to another machine and extracted. This will not register the install in any way, and so it must be launched by directly referencing the executables in the extracted directory, but it is sometimes a preferable approach in cases where installing the Python install manager is not possible or convenient.

In this way, Python runtimes can be installed and managed on a machine without access to the internet.

4.1.7. Uninstalling runtimes¶

$> py uninstall [-y|--yes] <TAG>...

Runtimes may be removed using the py uninstall command. One or more tags must be specified. Ranges are not supported here.

The --yes option bypasses the confirmation prompt before uninstalling.

Instead of passing tags individually, the --purge option may be specified. This will remove all runtimes managed by the Python install manager, including cleaning up the Start menu, registry, and any download caches. Runtimes that were not installed by the Python install manager will not be impacted, and neither will manually created configuration files.

$> py uninstall [-y|--yes] --purge

The Python install manager can be uninstalled through the Windows “Installed apps” settings page. This does not remove any runtimes, and they will still be usable, though the global python and py commands will be removed. Reinstalling the Python install manager will allow you to manage these runtimes again. To completely clean up all Python runtimes, run with --purge before uninstalling the Python install manager.

4.1.8. Configuration¶

Python install manager is configured with a hierarchy of configuration files, environment variables, command-line options, and registry settings. In general, configuration files have the ability to configure everything, including the location of other configuration files, while registry settings are administrator-only and will override configuration files. Command-line options override all other settings, but not every option is available.

This section will describe the defaults, but be aware that modified or overridden installs may resolve settings differently.

A global configuration file may be configured by an administrator, and would be read first. The user configuration file is stored at %AppData%\Python\pymanager.json (note that this location is under Roaming, not Local) and is read next, overwriting any settings from earlier files. An additional configuration file may be specified as the PYTHON_MANAGER_CONFIG environment variable or the --config command line option (but not both). These locations may be modified by administrative customization options listed later.

The following settings are those that are considered likely to be modified in normal use. Later sections list those that are intended for administrative customization.

Standard configuration options

Config Key	Environment Variable	설명
`default_tag`	PYTHON_MANAGER_DEFAULT¶	The preferred default version to launch or install. By default, this is interpreted as the most recent non-prerelease version from the CPython team.
`default_platform`	`PYTHON_MANAGER_DEFAULT_PLATFORM`	The preferred default platform to launch or install. This is treated as a suffix to the specified tag, such that `py -V:3.14` would prefer an install for `3.14-64` if it exists (and `default_platform` is `-64`), but will use `3.14` if no tagged install exists.
`logs_dir`	`PYTHON_MANAGER_LOGS`	The location where log files are written. By default, `%TEMP%`.
`automatic_install`	PYTHON_MANAGER_AUTOMATIC_INSTALL¶	True to allow automatic installs when using `py exec` to launch (or `py` when no runtimes are installed yet). Other commands will not automatically install, regardless of this setting. By default, true.
`include_unmanaged`	`PYTHON_MANAGER_INCLUDE_UNMANAGED`	True to allow listing and launching runtimes that were not installed by the Python install manager, or false to exclude them. By default, true.
`shebang_can_run_anything`	`PYTHON_MANAGER_SHEBANG_CAN_RUN_ANYTHING`	True to allow shebangs in `.py` files to launch applications other than Python runtimes, or false to prevent it. By default, true.
`shebang_templates`	(none)	Mapping from shebang line template to alternative command, such as `py -V:<tag>` or a substitute string. See Shebang lines for more details.
`log_level`	`PYMANAGER_VERBOSE`, `PYMANAGER_DEBUG`	Set the default level of output (0-50). By default, 20. Lower values produce more output. The environment variables are boolean, and may produce additional output during startup that is later suppressed by other configuration.
`confirm`	`PYTHON_MANAGER_CONFIRM`	True to confirm certain actions before taking them (such as uninstall), or false to skip the confirmation. By default, true.
`install.source`	`PYTHON_MANAGER_SOURCE_URL`	Override the index feed to obtain new installs from.
`install.enable_entrypoints`	(none)	True to generate global commands for installed packages (such as `pip.exe`). These are defined by the packages themselves. If set to false, only the Python interpreter has global commands created. By default, true. You should run `py install --refresh` after changing this setting.
`list.format`	`PYTHON_MANAGER_LIST_FORMAT`	Specify the default format used by the `py list` command. By default, `table`.
`install_dir`	(none)	Specify the root directory that runtimes will be installed into. If you change this setting, previously installed runtimes will not be usable unless you move them to the new location.
`global_dir`	(none)	Specify the directory where global commands (such as `python3.14.exe` and `pip.exe`) are stored. This directory should be added to your `PATH` to make the commands available from your terminal.
`download_dir`	(none)	Specify the directory where downloaded files are stored. This directory is a temporary cache, and can be cleaned up from time to time.

Dotted names should be nested inside JSON objects, for example, list.format would be specified as {"list": {"format": "table"}}.

4.1.9. 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. The python and py commands allow the same facilities to be used with Python scripts on Windows.

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

/usr/bin/env <ALIAS>
/usr/bin/env -S <ALIAS>
/usr/bin/<ALIAS>
/usr/local/bin/<ALIAS>
<ALIAS>

예를 들어, 스크립트의 첫 번째 줄이 다음과 같이 시작하면

#! /usr/bin/python

기본 파이썬이나 활성 가상 환경을 찾아서 사용합니다. 유닉스에서 작동하도록 작성된 많은 파이썬 스크립트에는 이미 이 줄이 있어서, 수정하지 않고도 이러한 스크립트를 런처에서 사용할 수 있습니다. 윈도우에서 유닉스에서 유용할 새 스크립트를 작성하면, /usr로 시작하는 셔뱅 줄 중 하나를 사용해야 합니다.

Any of the above virtual commands can have <ALIAS> replaced by an alias from an installed runtime. That is, any command generated in the global aliases directory (which you may have added to your PATH environment variable) can be used in a shebang, even if it is not on your PATH. This allows the use of shebangs like /usr/bin/python3.12 to select a particular runtime.

If no runtimes are installed, or if automatic installation is enabled, the requested runtime will be installed if necessary. See Configuration for information about configuration settings.

The /usr/bin/env form of shebang line will also search the PATH environment variable for unrecognized commands. This corresponds to the behaviour of the Unix env program, which performs the same search, but prefers launching known Python commands. A warning may be displayed when searching for arbitrary executables, and this search may be disabled by the shebang_can_run_anything configuration option.

Shebang lines that do not match any of patterns are treated as Windows executable paths that are absolute or relative to the directory containing the script file. This is a convenience for Windows-only scripts, such as those generated by an installer, since the behavior is not compatible with Unix-style shells. These paths may be quoted, and may include multiple arguments, after which the path to the script and any additional arguments will be appended. This functionality may be disabled by the shebang_can_run_anything configuration option.

Since version 26.3 of the Python install manager, custom shebang templates may be added to your configuration file. Add the shebang_templates object with one member for each template (the string to match) and the command to use when the template is matched. Most commands should be py -V:<tag> (or pyw) to launch one of your installed runtimes. The py -3.<version> form is also allowed, as is a plain py to launch the default. No other arguments are supported.

{
    "shebang_templates": {
        "/usr/bin/python": "py",
        "/usr/bin/my_custom_python": "py -V:MyCustomPython/3"
    }
}

If the substitute command is not py or pyw, it will be written back into the shebang and regular handling continues. If launching arbitrary executables is permitted, then providing a full path will allow you to redirect from Python to any executable. The template should match either the entire line (ignoring leading and trailing whitespace), or up to the first space in the shebang line.

참고

The behaviour of shebangs in the Python install manager is subtly different from the previous py.exe launcher, and the old configuration options no longer apply. If you are specifically reliant on the old behaviour or configuration, we recommend installing the legacy launcher. The legacy launcher’s py command will override PyManager’s one by default, and you will need to use pymanager commands for installing and uninstalling.

4.1.10. Advanced installation¶

For situations where an MSIX cannot be installed, such as some older administrative distribution platforms, there is an MSI available from the python.org downloads page. This MSI has no user interface, and can only perform per-machine installs to its default location in Program Files. It will attempt to modify the system PATH environment variable to include this install location, but be sure to validate this on your configuration.

참고

Windows Server 2019 is the only version of Windows that CPython supports that does not support MSIX. For Windows Server 2019, you should use the MSI.

Be aware that the MSI package does not bundle any runtimes, and so is not suitable for installs into offline environments without also creating an offline install index. See Offline installs and Administrative configuration for information on handling these scenarios.

Runtimes installed by the MSI are shared with those installed by the MSIX, and are all per-user only. The Python install manager does not support installing runtimes per-machine. To emulate a per-machine install, you can use py install --target=<shared location> as administrator and add your own system-wide modifications to PATH, the registry, or the Start menu.

When the MSIX is installed, but commands are not available in the PATH environment variable, they can be found under %LocalAppData%\Microsoft\WindowsApps\PythonSoftwareFoundation.PythonManager_3847v3x7pw1km or %LocalAppData%\Microsoft\WindowsApps\PythonSoftwareFoundation.PythonManager_qbz5n2kfra8p0, depending on whether it was installed from python.org or through the Windows Store. Attempting to run the executable directly from Program Files is not recommended.

To programmatically install the Python install manager, it is easiest to use WinGet, which is included with all supported versions of Windows:

$> winget install 9NQ7512CXL7T -e --accept-package-agreements --disable-interactivity

# Optionally run the configuration checker and accept all changes
$> py install --configure -y

To download the Python install manager and install on another machine, the following WinGet command will download the required files from the Store to your Downloads directory (add -d <location> to customize the output location). This also generates a YAML file that appears to be unnecessary, as the downloaded MSIX can be installed by launching or using the commands below.

$> winget download 9NQ7512CXL7T -e --skip-license --accept-package-agreements --accept-source-agreements

To programmatically install or uninstall an MSIX using only PowerShell, the Add-AppxPackage and Remove-AppxPackage PowerShell cmdlets are recommended:

$> Add-AppxPackage C:\Downloads\python-manager-25.0.msix
...
$> Get-AppxPackage PythonSoftwareFoundation.PythonManager | Remove-AppxPackage

The latest release can be downloaded and installed by Windows by passing the AppInstaller file to the Add-AppxPackage command. This installs using the MSIX on python.org, and is only recommended for cases where installing via the Store (interactively or using WinGet) is not possible.

$> Add-AppxPackage -AppInstallerFile https://www.python.org/ftp/python/pymanager/pymanager.appinstaller

Other tools and APIs may also be used to provision an MSIX package for all users on a machine, but Python does not consider this a supported scenario. We suggest looking into the PowerShell Add-AppxProvisionedPackage cmdlet, the native Windows PackageManager class, or the documentation and support for your deployment tool.

Regardless of the install method, users will still need to install their own copies of Python itself, as there is no way to trigger those installs without being a logged in user. When using the MSIX, the latest version of Python will be available for all users to install without network access.

Note that the MSIX downloadable from the Store and from the Python website are subtly different and cannot be installed at the same time. Wherever possible, we suggest using the above WinGet commands to download the package from the Store to reduce the risk of setting up conflicting installs. There are no licensing restrictions on the Python install manager that would prevent using the Store package in this way.

4.1.11. Administrative configuration¶

There are a number of options that may be useful for administrators to override configuration of the Python install manager. These can be used to provide local caching, disable certain shortcut types, override bundled content. All of the above configuration options may be set, as well as those below.

Configuration options may be overridden in the registry by setting values under HKEY_LOCAL_MACHINE\Software\Policies\Python\PyManager, where the value name matches the configuration key and the value type is REG_SZ. Note that this key can itself be customized, but only by modifying the core config file distributed with the Python install manager. We recommend, however, that registry values are used only to set base_config to a JSON file containing the full set of overrides. Registry key overrides will replace any other configured setting, while base_config allows users to further modify settings they may need.

Note that most settings with environment variables support those variables because their default setting specifies the variable. If you override them, the environment variable will no longer work, unless you override it with another one. For example, the default value of confirm is literally %PYTHON_MANAGER_CONFIRM%, which will resolve the variable at load time. If you override the value to yes, then the environment variable will no longer be used. If you override the value to %CONFIRM%, then that environment variable will be used instead.

Configuration settings that are paths are interpreted as relative to the directory containing the configuration file that specified them.

Administrative configuration options

Config Key	설명
`base_config`	The highest priority configuration file to read. Note that only the built-in configuration file and the registry can modify this setting.
`user_config`	The second configuration file to read.
`additional_config`	The third configuration file to read.
`registry_override_key`	Registry location to check for overrides. Note that only the built-in configuration file can modify this setting.
`bundled_dir`	Read-only directory containing locally cached files.
`install.fallback_source`	Path or URL to an index to consult when the main index cannot be accessed.
`install.enable_shortcut_kinds`	Comma-separated list of shortcut kinds to allow (e.g. `"pep514,start"`). Enabled shortcuts may still be disabled by `disable_shortcut_kinds`.
`install.disable_shortcut_kinds`	Comma-separated list of shortcut kinds to exclude (e.g. `"pep514,start"`). Disabled shortcuts are not reactivated by `enable_shortcut_kinds`.
`install.hard_link_entrypoints`	True to use hard links for global shortcuts to save disk space. If false, each shortcut executable is copied instead. After changing this setting, you must run `py install --refresh --force` to update existing commands. By default, true. Disabling this may be necessary for troubleshooting or systems that have issues with file links.
`pep514_root`	Registry location to read and write PEP 514 entries into. By default, `HKEY_CURRENT_USER\Software\Python`.
`start_folder`	Start menu folder to write shortcuts into. By default, `Python`. This path is relative to the user’s Programs folder.
`virtual_env`	Path to the active virtual environment. By default, this is `%VIRTUAL_ENV%`, but may be set empty to disable venv detection.
`shebang_can_run_anything_silently`	True to suppress visible warnings when a shebang launches an application other than a Python runtime.
`source_settings`	A mapping from source URL to settings specific to that index. When multiple configuration files include this section, URL settings are added or overwritten, but individual settings are not merged. These settings are currently only for index signatures.

4.1.12. Installing free-threaded binaries¶

Added in version 3.13.

Pre-built distributions of the free-threaded build are available by installing tags with the t suffix.

$> py install 3.14t
$> py install 3.14t-arm64
$> py install 3.14t-32

This will install and register as normal. If you have no other runtimes installed, then python will launch this one. Otherwise, you will need to use py -V:3.14t ... or, if you have added the global aliases directory to your PATH environment variable, the python3.14t.exe commands.

4.1.13. Index signatures¶

Added in version 26.2.

Index files may be signed to detect tampering. A signature is a catalog file at the same URL as the index with .cat added to the filename. The catalog file should contain the hash of its matching index file, and should be signed with a valid Authenticode signature. This allows standard tooling (on Windows) to generate a signature, and any certificate may be used as long as the client operating system already trusts its certification authority (root CA).

Index signatures are only downloaded and checked when the local configuration’s source_settings section includes the index URL and requires_signature is true, or the index JSON contains requires_signature set to true. When the setting exists in local configuration, even when false, settings in the index are ignored.

As well as requiring a valid signature, the required_root_subject and required_publisher_subject settings can further restrict acceptable signatures based on the certificate Subject fields. Any attribute specified in the configuration must match the attribute in the certificate (additional attributes in the certificate are ignored). Typical attributes are CN= for the common name, O= for the organizational unit, and C= for the publisher’s country.

Finally, the required_publisher_eku setting allows requiring that a specific Enhanced Key Usage (EKU) has been assigned to the publisher certificate. For example, the EKU 1.3.6.1.5.5.7.3.3 indicates that the certificate was intended for code signing (as opposed to server or client authentication). In combination with a specific root CA, this provides another mechanism to verify a legitimate signature.

This is an example source_settings section from a configuration file. In this case, the publisher of the feed is uniquely identified by the combination of the Microsoft Identity Verification root and the EKU assigned by that root. The signature for this case would be found at https://www.python.org/ftp/python/index-windows.json.cat.

{
  "source_settings": {
    "https://www.python.org/ftp/python/index-windows.json": {
      "requires_signature": true,
      "required_root_subject": "CN=Microsoft Identity Verification Root Certificate Authority 2020",
      "required_publisher_subject": "CN=Python Software Foundation",
      "required_publisher_eku": "1.3.6.1.4.1.311.97.608394634.79987812.305991749.578777327"
    }
  }
}

The same settings could be specified in the index.json file instead. In this case, the root and EKU are omitted, meaning that the signature must be valid and have a specific common name in the publisher’s certificate, but no other checks are used.

{
  "requires_signature": true,
  "required_publisher_subject": "CN=Python Software Foundation",
  "versions": [
    // ...
  ]
}

When settings from inside a feed are used, the user is notified and the settings are shown in the log file or verbose output. It is recommended to copy these settings into a local configuration file for feeds that will be used frequently, so that unauthorised modifications to the feed cannot disable verification.

It is not possible to override the location of the signature file in the feed or through a configuration file. Administrators can provide their own source_settings in a mandatory configuration file (see Administrative configuration).

If signature validation fails, you will be notified and prompted to continue. When interactive confirmation is not allowed (for example, because --yes was specified), it will always abort. To use a feed with invalid configuration in this scenario, you must provide a configuration file that disables signature checking for that feed.

"source_settings": {
  "https://www.example.com/feed-with-invalid-signature.json": {
    "requires_signature": false
  }
}

4.1.14. Troubleshooting¶

If your Python install manager does not seem to be working correctly, please work through these tests and fixes to see if it helps. If not, please report an issue at our bug tracker, including any relevant log files (written to your %TEMP% directory by default).

Troubleshooting

Symptom	Things to try
`python` gives me a “command not found” error or opens the Store app when I type it in my terminal.	Did you install the Python install manager?
	Click Start, open “Manage app execution aliases”, and check that the aliases for “Python (default)” are enabled. If they already are, try disabling and re-enabling to refresh the command. The “Python (default windowed)” and “Python install manager” commands may also need refreshing.
	Check that the `py` and `pymanager` commands work.
	Ensure your `PATH` variable contains the entry for `%UserProfile%\AppData\Local\Microsoft\WindowsApps`. The operating system includes this entry once by default, after other user paths. If removed, shortcuts will not be found.
`py` gives me a “command not found” error when I type it in my terminal.	Did you install the Python install manager?
	Click Start, open “Manage app execution aliases”, and check that the aliases for “Python (default)” are enabled. If they already are, try disabling and re-enabling to refresh the command. The “Python (default windowed)” and “Python install manager” commands may also need refreshing.
	Ensure your `PATH` variable contains the entry for `%UserProfile%\AppData\Local\Microsoft\WindowsApps`. The operating system includes this entry once by default, after other user paths. If removed, shortcuts will not be found.
`py` gives me a “can’t open file” error when I type commands in my terminal.	This usually means you have the legacy launcher installed and it has priority over the Python install manager. To remove, click Start, open “Installed apps”, search for “Python launcher” and uninstall it.
`python` doesn’t launch the same runtime as `py`	Click Start, open “Installed apps”, look for any existing Python runtimes, and either remove them or Modify and disable the `PATH` options.
	Click Start, open “Manage app execution aliases”, and check that your `python.exe` alias is set to “Python (default)”
`python` and `py` don’t launch the runtime I expect	Check your `PYTHON_MANAGER_DEFAULT` environment variable or `default_tag` configuration. The `py list` command will show your default based on these settings.
	Installs that are managed by the Python install manager will be chosen ahead of unmanaged installs. Use `py install` to install the runtime you expect, or configure your default tag.
	Prerelease and experimental installs that are not managed by the Python install manager may be chosen ahead of stable releases. Configure your default tag or uninstall the prerelease runtime and reinstall it using `py install`.
`pythonw` or `pyw` don’t launch the same runtime as `python` or `py`	Click Start, open “Manage app execution aliases”, and check that your `pythonw.exe` and `pyw.exe` aliases are consistent with your others.
`pip` gives me a “command not found” error when I type it in my terminal.	Have you activated a virtual environment? Run the `.venv\Scripts\activate` script in your terminal to activate.
	The package may be available but missing the generated executable. We recommend using the `python -m pip` command instead. Running `py install --refresh` and ensuring that the global shortcuts directory is on `PATH` (it will be shown in the command output if it is not) should make commands such as `pip` (and other installed packages) available.
I installed a package with `pip` but its command is not found.	Have you activated a virtual environment? Run the `.venv\Scripts\activate` script in your terminal to activate.
	New packages do not automatically have global shortcuts created by the Python install manager. Similarly, uninstalled packages do not have their shortcuts removed. Run `py install --refresh` to update the global shortcuts for newly installed packages.
Typing `script-name.py` in the terminal opens in a new window.	This is a known limitation of the operating system. Either specify `py` before the script name, create a batch file containing `@py "%~dpn0.py" %*` with the same name as the script, or install the legacy launcher and select it as the association for scripts.
Drag-dropping files onto a script doesn’t work	This is a known limitation of the operating system. It is supported with the legacy launcher, or with the Python install manager when installed from the MSI.
I have installed the Python install manager multiple times.	It is possible to install from the Store or WinGet, from the MSIX on the Python website, and from the MSI, all at once. They are all compatible and will share configuration and runtimes.
	See the earlier Advanced installation section for ways to uninstall the install manager other than the typical Installed Apps (Add and Remove Programs) settings page.
My old `py.ini` settings no longer work.	The new Python install manager no longer supports this configuration file or its settings, and so it will be ignored. See Configuration for information about configuration settings.

4.2. 내장 가능한 패키지¶

Added in version 3.5.

내장된 배포는 최소 파이썬 환경을 포함하는 ZIP 파일입니다. 최종 사용자가 직접 액세스하기보다는, 다른 응용 프로그램의 일부로 작동하기 위한 것입니다.

To install an embedded distribution, we recommend using py install with the --target option:

$> py install 3.14-embed --target=<directory>

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, python313.dll, python.exe and pythonw.exe are all provided. Tcl/tk (including all dependents, such as Idle), pip and the Python documentation are not included.

A default ._pth file is included, which further restricts the default search paths (as described below in 모듈 찾기). This file is intended for embedders to modify as necessary.

제삼자 패키지는 내장된 배포와 함께 응용 프로그램 설치 프로그램이 설치해야 합니다. 일반 파이썬 설치처럼 종속성을 관리하기 위해 pip를 사용하는 것은 이 배포에서 지원되지 않지만, 주의를 기울이면 자동 업데이트를 위해 pip를 포함하고 사용할 수 있습니다. 일반적으로, 제삼자 패키지는 개발자가 사용자에게 업데이트를 제공하기 전에 최신 버전과의 호환성을 보장할 수 있도록 응용 프로그램의 일부로 처리되어야 합니다 (“벤더링(vendoring)”).

이 배포에 권장되는 두 가지 사용 사례가 아래에 설명되어 있습니다.

4.2.1. Python application¶

파이썬으로 작성된 응용 프로그램이 반드시 사용자가 그 사실을 인식하도록 할 필요는 없습니다. 이 경우 내장된 배포를 사용하여 설치 패키지에 파이썬의 내부 버전을 포함할 수 있습니다. 얼마나 투명해야 하는지(또는 반대로, 얼마나 전문적으로 보여야 하는지)에 따라, 두 가지 옵션이 있습니다.

특수 실행 파일을 런처로 사용하려면 약간의 코딩이 필요하지만, 사용자에게 가장 투명한 경험을 제공합니다. 사용자 정의된 런처를 사용하면, 프로그램이 파이썬에서 실행되고 있다는 명백한 표시가 없습니다: 아이콘을 사용자 정의하고, 회사와 버전 정보를 지정할 수 있으며 파일 연결이 제대로 작동합니다. 대부분의 경우, 사용자 정의 런처는 하드 코딩된 명령 줄을 사용하여 Py_Main을 호출할 수 있어야 합니다.

더 간단한 방법은 필요한 명령 줄 인자를 사용하여 python.exe나 pythonw.exe를 직접 호출하는 배치 파일이나 생성된 바로 가기를 제공하는 것입니다. 이 경우, 응용 프로그램은 실제 이름이 아닌 파이썬으로 표시되며, 사용자는 실행 중인 다른 파이썬 프로세스나 파일 연결과 구별하는 데 어려움을 겪을 수 있습니다.

후자의 접근 방식에서는, 패키지를 파이썬 실행 파일과 함께 디렉터리로 설치하여 경로에서 사용할 수 있도록 해야 합니다. 특수 런처를 사용하면, 응용 프로그램을 시작하기 전에 검색 경로를 지정할 수 있어서 패키지를 다른 위치에 배치할 수 있습니다.

4.2.2. 파이썬 내장하기¶

네이티브 코드로 작성된 응용 프로그램에는 종종 어떤 형태의 스크립팅 언어가 필요하며, 내장된 파이썬 배포를 이러한 목적으로 사용할 수 있습니다. 일반적으로, 대부분의 응용 프로그램은 네이티브 코드로 되어 있으며, 일부가 python.exe를 호출하거나 python3.dll을 직접 사용합니다. 두 경우 모두, 내장된 배포를 응용 프로그램 설치의 하위 디렉터리로 추출하면 로드할 수 있는 파이썬 인터프리터를 제공하기에 충분합니다.

응용 프로그램 사용과 마찬가지로, 인터프리터를 초기화하기 전에 검색 경로를 지정할 기회가 있어서 패키지를 임의의 위치에 설치할 수 있습니다. 그 외에는, 내장된 배포와 일반 설치를 사용하는 것 간에 근본적인 차이점은 없습니다.

4.3. nuget.org 패키지¶

Added in version 3.5.2.

nuget.org 패키지는 시스템 전체에 파이썬이 설치되지 않은 지속적인 통합과 빌드 시스템에 사용하기 위한 축소된 크기의 파이썬 환경입니다. 너겟은 “.NET 용 패키지 관리자”이지만, 빌드 타임 도구가 포함된 패키지에서도 완벽하게 작동합니다.

너겟 사용에 대한 최신 정보를 보려면 nuget.org를 방문하십시오. 다음은 파이썬 개발자에게 충분한 요약입니다.

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

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

특정 버전을 선택하려면, -Version 3.x.y를 추가하십시오. 출력 디렉터리는 .에서 변경될 수 있으며, 패키지는 하위 디렉터리에 설치됩니다. 기본적으로, 하위 디렉터리의 이름은 패키지와 같으며, -ExcludeVersion 옵션이 없으면 이 이름에 설치된 특정 버전이 포함됩니다. 하위 디렉터리에는 파이썬 설치가 포함된 tools 디렉터리가 있습니다:

# -ExcludeVersion 없이
> .\python.3.5.2\tools\python.exe -V
Python 3.5.2

# -ExcludeVersion 포함
> .\python\tools\python.exe -V
Python 3.5.2

일반적으로, 너겟 패키지는 업그레이드할 수 없으며, 최신 버전을 나란히 설치하고 전체 경로를 사용하여 참조해야 합니다. 또는, 패키지 디렉터리를 수동으로 삭제하고 다시 설치하십시오. 많은 CI 시스템은 빌드 간에 파일을 보존하지 않으면 이 작업을 자동으로 수행합니다.

tools 디렉터리와 함께 build\native 디렉터리가 있습니다. 여기에는 파이썬 설치를 참조하기 위해 C++ 프로젝트에서 사용할 수 있는 MSBuild 속성 파일 python.props가 포함되어 있습니다. 설정을 포함하면 빌드에서 자동으로 헤더와 임포트 라이브러리를 사용합니다.

nuget.org의 패키지 정보 페이지는 64비트 버전의 경우 www.nuget.org/packages/python, 32비트 버전의 경우 www.nuget.org/packages/pythonx86 그리고 ARM64 버전의 경우 www.nuget.org/packages/pythonarm64입니다.

4.3.1. 자유 스레드 패키지¶

Added in version 3.13.

Packages containing free-threaded binaries are named python-freethreaded for the 64-bit version, pythonx86-freethreaded for the 32-bit version, and pythonarm64-freethreaded for the ARM64 version. These packages contain both the python3.13t.exe and python.exe entry points, both of which run free threaded.

4.4. 대체 번들¶

표준 CPython 배포 외에도, 추가 기능을 포함하는 수정된 패키지가 있습니다. 다음은 많이 사용되는 버전과 주요 기능 목록입니다:

ActivePython

다중 플랫폼 호환성, 설명서, PyWin32가 있는 설치 프로그램

Anaconda

인기 있는 과학 모듈(가령 numpy, scipy 및 pandas)과 conda 패키지 관리자.

Enthought Deployment Manager

“The Next Generation Python Environment and Package Manager”.

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

WinPython

사전 빌드된 과학 패키지와 패키지 빌드를 위한 도구가 포함된 윈도우 전용 배포.

이러한 패키지들은 최신 버전의 파이썬이나 기타 라이브러리를 포함하지 않을 수 있으며, 핵심 파이썬 팀에서 유지 관리하거나 지원하지 않음에 유의하십시오.

4.5. Supported Windows versions¶

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.16 supports Windows 10 and newer. If you require Windows 7 support, please install Python 3.8. If you require Windows 8.1 support, please install Python 3.12.

4.6. Removing the MAX_PATH limitation¶

윈도우는 역사적으로 경로 길이를 260자로 제한했습니다. 이는 이보다 긴 경로는 결정(resolve)되지 않고 에러가 발생함을 의미합니다.

In the latest versions of Windows, this limitation can be expanded to over 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.

이는 open() 함수, os 모듈 및 대부분의 다른 경로 기능이 260자보다 긴 경로를 받아들이고 반환할 수 있도록 합니다.

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

4.7. UTF-8 모드¶

Added in version 3.7.

버전 3.15에서 변경: Python UTF-8 mode is now enabled by default (PEP 686).

윈도우는 여전히 시스템 인코딩에 레거시 인코딩을 사용합니다 (ANSI 코드 페이지). 파이썬은 이를 텍스트 파일의 기본 인코딩에 이를 사용합니다 (예를 들어 locale.getencoding()).

UTF-8은 인터넷과 WSL(Windows Subsystem for Linux)을 포함한 대부분의 유닉스 시스템에서 널리 사용되기 때문에 문제가 발생할 수 있습니다.

The Python UTF-8 Mode, enabled by default, can help by changing the default text encoding to UTF-8. When the UTF-8 mode is enabled, you can still use the system encoding (the ANSI Code Page) via the “mbcs” codec.

You can disable the Python UTF-8 Mode via the -X utf8=0 command line option, or the PYTHONUTF8=0 environment variable. See PYTHONUTF8 for disabling UTF-8 mode, and Python install manager for how to modify environment variables.

힌트

Adding PYTHONUTF8={0,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.

참고

UTF-8 모드가 비활성화된 경우에도, 파이썬은 윈도우에서 기본적으로 다음을 위해 UTF-8을 사용합니다:

표준 I/O를 포함한 콘솔 I/O (자세한 내용은 PEP 528을 참조하십시오).
파일 시스템 인코딩 (자세한 내용은 PEP 529를 참조하십시오).

4.8. 모듈 찾기¶

These notes supplement the description at The initialization of the sys.path module search path with detailed Windows notes.

._pth 파일이 없을 때, 윈도우에서 sys.path를 채우는 방법은 다음과 같습니다:

시작에 현재 디렉터리에 해당하는 빈 항목이 추가됩니다.
환경 변수에 설명된 대로, 환경 변수 PYTHONPATH가 존재하면, 해당 항목이 다음에 추가됩니다. 윈도우에서, 이 변수의 경로는 드라이브 식별자(C:\ 등)에 사용되는 콜론과 구별하기 위해 세미콜론으로 구분되어야 합니다.
추가 “응용 프로그램 경로”는 HKEY_CURRENT_USER와 HKEY_LOCAL_MACHINE 하이브 모두의 아래에 \SOFTWARE\Python\PythonCore{version}\PythonPath의 하위 키로 레지스트리에 추가될 수 있습니다. 세미콜론으로 구분된 경로 문자열을 기본값으로 사용하는 하위 키는 각 경로가 sys.path에 추가되도록 합니다. (알려진 모든 설치 프로그램은 HKLM 만 사용하므로, HKCU는 일반적으로 비어 있음에 유의하십시오.)
환경 변수 PYTHONHOME이 설정되면, “파이썬 홈”으로 간주합니다. 그렇지 않으면, 메인 파이썬 실행 파일의 경로를 사용하여 “랜드마크 파일”(Lib\os.py나 pythonXY.zip)을 찾아 “파이썬 홈”을 추론합니다. 파이썬 홈이 발견되면, sys.path에 추가되는 관련 하위 디렉터리(Lib, plat-win 등)는 해당 폴더를 기반으로 합니다. 그렇지 않으면, 핵심 파이썬 경로가 레지스트리에 저장된 PythonPath에서 구성됩니다.
파이썬 홈을 찾을 수 없고, 환경에 PYTHONPATH가 지정되어 있지 않고, 레지스트리 항목을 찾을 수 없으면, 상대 항목의 기본 경로(예를 들어 .\Lib;.\plat-win 등)가 사용됩니다.

pyvenv.cfg 파일이 메인 실행 파일과 함께 또는 실행 파일보다 한 수준 위의 디렉터리에서 발견되면, 다음 변형이 적용됩니다:

home이 절대 경로이고 PYTHONHOME이 설정되지 않으면, 홈 위치를 추론할 때 메인 실행 파일에 대한 경로 대신 이 경로가 사용됩니다.

이 모든 것의 최종 결과는 다음과 같습니다:

python.exe 또는 기본 파이썬 디렉터리 (설치된 버전 또는 PCbuild 디렉터리에서 직접)에서 다른 .exe를 실행할 때 핵심 경로가 추론되고 레지스트리의 핵심 경로가 무시됩니다. 레지스트리의 다른 “응용 프로그램 경로”는 항상 읽습니다.
파이썬이 다른 .exe(다른 디렉터리, COM을 통한 내장, 등)에서 호스팅 될 때, “파이썬 홈”이 추론되지 않아서, 레지스트리의 핵심 경로가 사용됩니다. 레지스트리의 다른 “응용 프로그램 경로”는 항상 읽힙니다.
파이썬이 홈을 찾을 수 없고 레지스트리 값이 없으면 (고정된(frozen) .exe, 아주 이상한 설치 설정), 일부 기본 (하지만 상대) 경로를 얻게 됩니다.

파이썬을 응용 프로그램이나 배포에 번들로 포함하려는 사용자를 위해, 다음 조언은 다른 설치와의 충돌을 방지합니다:

포함할 디렉터리가 포함된 실행 파일과 함께 ._pth 파일을 포함합니다. 이것은 레지스트리와 환경 변수에 나열된 경로를 무시하고, import site가 나열되지 않는 한 site도 무시합니다.
여러분 자신의 실행 파일에서 python3.dll이나 python37.dll을 로드하면, Py_InitializeFromConfig() 전에 PyConfig.module_search_paths 를 명시적으로 설정하십시오.
응용 프로그램에서 python.exe를 시작하기 전에 PYTHONPATH를 지우거나 덮어쓰고 PYTHONHOME를 설정하십시오.
이전 제안을 사용할 수 없으면 (예를 들어, 사용자가 python.exe를 직접 실행할 수 있는 배포판이면), 랜드마크 파일(Lib\os.py)이 설치 디렉터리에 있도록 하십시오. (ZIP 파일 내에서는 감지되지 않지만, 대신 올바른 이름의 ZIP 파일은 감지됨에 유의하십시오.)

이렇게 하면 시스템 전체 설치의 파일이 응용 프로그램과 함께 번들로 제공되는 표준 라이브러리의 복사본보다 우선하지 않습니다. 그렇지 않으면, 사용자가 여러분의 응용 프로그램을 사용하는 데 문제가 발생할 수 있습니다. 다른 제안은 레지스트리의 비표준 경로와 사용자 site-packages에 여전히 취약할 수 있어서, 첫 번째 제안이 가장 좋음에 유의하십시오.

버전 3.6에서 변경: ._pth 파일 지원을 추가하고 pyvenv.cfg에서 applocal 옵션을 제거합니다.

버전 3.6에서 변경: 실행 파일에 직접 인접할 때 잠재적인 랜드마크로 pythonXX.zip을 추가합니다.

버전 3.6부터 폐지됨: Modules(PythonPath가 아닙니다) 아래의 레지스트리에 지정된 모듈은 importlib.machinery.WindowsRegistryFinder 로 임포트 할 수 있습니다. 이 파인더는 윈도우 3.6.0과 이전 버전에서 활성화되지만, 향후에는 sys.meta_path에 명시적으로 추가해야 할 수도 있습니다.

4.9. 추가 모듈¶

파이썬이 모든 플랫폼 간에 이식성 있는 것을 목표로 하지만, 윈도우에만 고유한 기능이 있습니다. 이러한 기능을 사용하기 위한 표준 라이브러리와 외부에 있는 두 개의 모듈과 스니펫(snippets)이 존재합니다.

윈도우 특정 표준 모듈은 MS 윈도우 특정 서비스에 설명되어 있습니다.

4.9.1. PyWin32¶

Mark Hammond의 PyWin32 모듈은 고급 윈도우 특정 지원을 위한 모듈 모음입니다. 여기에는 다음을 위한 유틸리티가 포함됩니다:

Component Object Model (COM)
Win32 API 호출
레지스트리
이벤트 로그
Microsoft Foundation Classes (MFC) 사용자 인터페이스

PythonWin은 PyWin32와 함께 제공되는 샘플 MFC 응용 프로그램입니다. 디버거가 내장된 내장할 수 있는 IDE입니다.

Win32 How Do I…?: 저자: Tim Golden
Python and COM: 저자: David와 Paul Boddie

4.9.2. cx_Freeze¶

cx_Freeze는 파이썬 스크립트를 실행 가능한 윈도우 프로그램(*.exe 파일)으로 래핑합니다. 이렇게 하면, 사용자가 파이썬을 설치할 필요 없는 응용 프로그램을 배포할 수 있습니다.

4.10. 윈도우에서 파이썬 컴파일하기¶

CPython을 직접 컴파일하려면, 먼저 소스를 가져와야 합니다. 최신 릴리스의 소스를 다운로드하거나 최신 버전을 체크아웃할 수 있습니다.

소스 트리에는 공식 파이썬 릴리스를 빌드하는 데 사용되는 컴파일러인 Microsoft Visual Studio 용 빌드 솔루션과 프로젝트 파일이 포함되어 있습니다. 이 파일들은 PCbuild 디렉터리에 있습니다.

빌드 프로세스에 대한 일반 정보는 PCbuild/readme.txt를 확인하십시오.

확장 모듈에 대해서는, 윈도우에서 C와 C++ 확장 빌드하기를 참조하십시오.