4. Uso de Python en Windows
***************************

Este documento pretende dar una visión general del comportamiento
específico de Windows que se debería conocer al usar Python en
Microsoft Windows.

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 El paquete de 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 El paquete incrustable 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              | Descripción                       |
|===================================|===================================|===================================|
| "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_UNMANAGE  | True to allow listing and         |
|                                   | D"                                | 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_  | True to allow shebangs in ".py"   |
|                                   | ANYTHING"                         | 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",              | Set the default level of output   |
|                                   | "PYMANAGER_DEBUG"                 | (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>"

Por ejemplo, si la primera línea del script comienza con

   #! /usr/bin/python

The default Python or an active virtual environment 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 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.

Nota:

  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.

Nota:

  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_3847v3x7
pw1km" or "%LocalAppData%\Microsoft\WindowsApps\PythonSoftwareFoundat
ion.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                                         | Descripción                                        |
|====================================================|====================================================|
| "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   | Did you install the Python install manager?        |
| opens the Store app when I type it in my terminal. |                                                    |
+----------------------------------------------------+----------------------------------------------------+
|                                                    | 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\WindowsApp  |
|                                                    | s". 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   | Did you install the Python install manager?        |
| type it in my terminal.                            |                                                    |
+----------------------------------------------------+----------------------------------------------------+
|                                                    | 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\WindowsApp  |
|                                                    | s". 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     | This usually means you have the legacy launcher    |
| type commands in my terminal.                      | 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       | Check your "PYTHON_MANAGER_DEFAULT" environment    |
| expect                                             | 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   | Click Start, open "Manage app execution aliases",  |
| as "python" or "py"                                | 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  | Have you activated a virtual environment? Run the  |
| type it in my terminal.                            | ".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   | Have you activated a virtual environment? Run the  |
| is not found.                                      | ".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 | This is a known limitation of the operating        |
| new window.                                        | 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        | It is possible to install from the Store or        |
| multiple times.                                    | 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. El paquete incrustable
===========================

Added in version 3.5.

La distribución incrustable consiste en un archivo ZIP que contiene un
mínimo entorno de Python. Está destinado a ser usado como parte de
otra aplicación, en lugar de ser accedido directamente por los
usuarios finales.

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 Encontrar módulos). This
file is intended for embedders to modify as necessary.

Los paquetes de terceros deben ser instalados por el instalador de la
aplicación junto a la distribución incrustada. El uso de pip para
administrar dependencias como en una instalación de Python regular no
es soportado por esta distribución, aunque con cierto cuidado es
posible incluir y usar pip para automatizar las actualizaciones. En
general, los paquetes de terceros deben ser tratados como parte de la
aplicación ("vendoring") para que el desarrollador pueda asegurar la
compatibilidad con las nuevas versiones antes de proporcionar
actualizaciones a los usuarios.

Los dos casos de uso recomendados para esta distribución se describen
a continuación.


4.2.1. Python application
-------------------------

Una aplicación escrita en Python no necesariamente requiere que los
usuarios sean conscientes de ese hecho. La distribución incrustada
puede ser usada en este caso para incluir una versión privada de
Python en un paquete de instalación. Dependiendo de lo transparente
que deba ser (o por el contrario, de lo profesional que deba parecer),
hay dos opciones.

El uso de un ejecutable especializado como lanzador requiere algo de
código, pero proporciona la experiencia más transparente para los
usuarios. Con un lanzador personalizado, no hay indicadores obvios de
que el programa se ejecuta en Python: los íconos pueden ser
personalizados, se puede especificar información de la compañía y de
la versión, y las asociaciones de archivos se comportan correctamente.
En la mayoría de los casos, un lanzador personalizado debería
simplemente poder invocar "Py_Main" utilizando una línea de comandos
codificada.

El enfoque más simple es proporcionar un archivo por lotes o un acceso
directo generado que directamente invoque "python.exe" o "pythonw.exe"
con los argumentos de línea de comandos requeridos. En este caso, la
aplicación aparecerá como Python y no con su nombre real, y los
usuarios podrían tener problemas para distinguirla de otros procesos
Python en ejecución o asociaciones de archivos.

Con este último enfoque, los paquetes deben instalarse como
directorios junto al ejecutable de Python para asegurar su
disponibilidad en la ruta. Con el lanzador especializado, los paquetes
pueden encontrarse en otras ubicaciones ya que hay oportunidad de
especificar la ruta de búsqueda antes de iniciar la aplicación.


4.2.2. Incrustar Python
-----------------------

Las aplicaciones escritas en código nativo frecuentemente requieren
algún tipo de lenguaje de scripting, y la distribución de Python
incrustada puede ser utilizada con ese propósito. En general, la
mayoría de la aplicación utiliza código nativo, y alguna parte
invocará "python.exe" o usará "python3.dll" directamente. Para
cualquiera de estos casos, la extracción de la distribución
incrustable a un subdirectorio de la instalación de la aplicación es
suficiente para proporcionar un intérprete de Python invocable.

Al igual que con el uso de la aplicación, los paquetes pueden ser
instalados en cualquier ubicación, ya que existe la posibilidad de
especificar rutas de búsqueda antes de inicializar el intérprete. Más
allá de esto, no existen diferencias fundamentales entre el uso de la
distribución incrustada y una instalación normal.


4.3. El paquete de nuget.org
============================

Added in version 3.5.2.

El paquete de nuget.org es un entorno Python de tamaño reducido
destinado a usarse en sistemas de integración continua y compilación
que no posean una instalación de Python a nivel de sistema. Si bien
nuget es "el administrador de paquetes para .NET", también funciona
perfectamente para paquetes que contienen herramientas de tiempo de
compilación.

Visite nuget.org para obtener la información más actualizada sobre
cómo usar nuget. Lo que sigue es un resumen que es suficiente para
desarrolladores Python.

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 .

Para seleccionar una versión en particular, agregue un "-Version
3.x.y". El directorio de salida se puede cambiar de "." y el paquete
se instalará en un subdirectorio. De forma predeterminada, el
subdirectorio tiene el mismo nombre que el paquete y, sin la opción
"-ExcludeVersion", este nombre incluirá la versión específica
instalada. Dentro del subdirectorio hay un directorio "tools" que
contiene la instalación de Python:

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

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

En general, los paquetes nuget no son actualizables, y versiones más
nuevas deben ser instaladas en paralelo y referenciadas usando la ruta
completa. Otra opción es borrar el directorio del paquete de forma
manual e instalarlo de nuevo. Muchos sistemas de CI harán esto
automáticamente si no mantienen archivos entre compilaciones.

Junto al directorio "tools" está el directorio "build\native". Este
contiene un archivo de propiedades MSBuild "Python.props" que puede
ser usado en un proyecto C++ para referenciar la instalación de
Python. Al incluir las configuraciones, automáticamente se usarán los
encabezados y se importarán las bibliotecas en la compilación.

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


4.3.1. Free-threaded packages
-----------------------------

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. Distribuciones alternativas
================================

Además de la distribución estándar de CPython, hay paquetes
modificados que incluyen funcionalidad adicional. La siguiente es una
lista de versiones populares y sus características clave:

ActivePython
   Instalador compatible con múltiples plataformas, documentación,
   PyWin32

Anaconda
   Módulos científicos populares (como numpy, scipy y pandas) y el
   gestor de paquetes "conda".

Enthought Deployment Manager
   "El administrador de paquetes y entorno de Python de próxima
   generación".

   Anteriormente, Enthought proporcionaba Canopy, pero llegó al final
   de su vida en2016.

WinPython
   Distribución específica para Windows con paquetes científicos
   precompilados y herramientas para construir paquetes.

Tenga en cuenta que estos paquetes pueden no incluir la última versión
de Python u otras bibliotecas, y no son mantenidos ni respaldados por
el equipo central de Python.


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
=====================================

Windows históricamente ha limitado la longitud de las rutas a 260
caracteres. Esto significaba que rutas de mayor longitud no
resolverían y se producirían errores.

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

Esto permite que la función "open()", el módulo "os" y la mayoría de
las demás funciones de ruta acepten y retornen rutas de más de 260
caracteres.

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


4.7. Modo UTF-8
===============

Added in version 3.7.

Distinto en la versión 3.15: Python UTF-8 mode is now enabled by
default (**PEP 686**).

Windows todavía usa codificaciones heredadas para la codificación del
sistema (la página de códigos ANSI). Python lo usa para la
codificación predeterminada de archivos de texto (por ejemplo,
"locale.getencoding()").

Esto puede causar problemas porque UTF-8 es ampliamente utilizado en
internet y en la mayoría de los sistemas Unix, incluido WSL
(subsistema de Windows para 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.

Consejo:

  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.

Nota:

  Aún con el modo UTF-8 desactivado, Python utiliza UTF-8 de forma
  predeterminada en Windows para:

  * E/S de consola, incluida la E/S estándar (consultar **PEP 528**
    para más detalles).

  * La *codificación del sistema* (vea **PEP 529** para más detalles).


4.8. Encontrar módulos
======================

Estas notas complementan la descripción en La inicialización de la
ruta de búsqueda de módulo de sys.path con notas detalladas de
Windows.

Cuando no se encuentre ningún archivo "._pth", así es como "sys.path"
es completado en Windows:

* Se agrega una entrada vacía al comienzo, que corresponde al
  directorio actual.

* Si existe la variable de entorno "PYTHONPATH", de acuerdo a lo
  descrito en Variables de entorno, sus entradas se agregan a
  continuación. Tenga en cuenta que en Windows, las rutas en esta
  variable deben estar separadas por punto y coma (;), para
  distinguirlas de los dos puntos utilizados en los identificadores de
  disco ("C:\", etc.).

* Se pueden agregar al registro "rutas de aplicación" adicionales como
  subclaves de "\SOFTWARE\Python\PythonCore{version}\PythonPath" bajo
  los subárboles "HKEY_CURRENT_USER" y "HKEY_LOCAL_MACHINE". Las
  subclaves que contienen un valor por defecto compuesto por cadenas
  de ruta separadas por punto y coma causan que cada una de esas rutas
  sea agregada a "sys.path". (Tenga en cuenta que todos los
  instaladores conocidos solo utilizan HKLM, por lo que HKCU
  comúnmente se encuentra vacío.)

* Si se configura la variable de entorno "PYTHONHOME", es asumida como
  el "Python Home" (el directorio de origen de Python). De lo
  contrario, la ruta del ejecutable principal de Python es utilizada
  para ubicar un "archivo de referencia" (ya sea "Lib\os.py" o
  "pythonXY.zip") para deducir el "Python Home". Si el directorio de
  origen de Python es encontrado, los subdirectorios relevantes que se
  agregan a "sys.path" ("Lib", "plat-win", etc.) se basan en ese
  directorio. Por el contrario, la ruta principal de Python se
  construye a partir del PythonPath guardado en el registro.

* Si el Python Home no puede ser ubicado, "PYTHONPATH" no está
  especificado en el entorno y no se encuentra ninguna entrada en el
  registro, se usa una ruta predeterminada con entradas relativas (por
  ej. ".\Lib;.\plat-win", etc.).

Si se encuentra el archivo "pyvenv.cfg" junto al ejecutable principal
o en el directorio un nivel arriba del ejecutable, se aplica la
siguiente variación:

* Si "home" es una ruta absoluta y "PYTHONHOME" no está configurada,
  se usa esta ruta en lugar de la ruta al ejecutable principal para
  deducir la ubicación del directorio de origen.

El resultado final de todo esto es:

* Cuando se ejecuta "python.exe", o cualquier otro .exe en el
  directorio principal de Python (tanto la versión instalada como
  directamente desde el directorio PCbuild), se deduce la ruta
  principal, y se ignoran las rutas principales en el registro.
  Siempre se leen otras "rutas de aplicación" del registro.

* Cuando se aloja Python en otro .exe (distinto directorio, incrustado
  mediante COM, etc.), el "Python Home" no se deduce, y se utiliza la
  ruta principal del registro. Siempre se leen otras "rutas de
  aplicación" del registro.

* Si Python no puede encontrar su directorio de origen y no hay
  valores en el registro (un .exe congelado, una muy rara
  configuración de instalación) se obtiene una ruta relativa
  predeterminada.

Para aquellos que quieran incluir Python en su aplicación o
distribución, los siguientes consejos evitarán conflictos con otras
instalaciones:

* Incluya un archivo "._pth" junto al ejecutable, que contenga los
  directorios a incluir. Esto hará que se ignoren las rutas enumeradas
  en el registro y en las variables de entorno, y que también se
  ignore "site" a menos que se especifique "import site".

* If you are loading "python3.dll" or "python37.dll" in your own
  executable, explicitly set "PyConfig.module_search_paths" before
  "Py_InitializeFromConfig()".

* Limpie y/o sobrescriba "PYTHONPATH" y configure "PYTHONHOME" antes
  de iniciar "python.exe" desde su aplicación.

* Si no se pueden utilizar las sugerencias previas (por ejemplo, en
  una distribución que permite a los usuarios ejecutar "python.exe"
  directamente), hay que asegurarse de que el archivo de referencia
  ("Lib\os.py") exista en el directorio de instalación. (Tener en
  cuenta que este no será detectado dentro de un archivo ZIP, pero si
  se detectará un ZIP correctamente nombrado.)

Esto asegura que los archivos de una instalación del sistema no
tendrán precedencia por sobre la copia de la biblioteca estándar
incluida en su aplicación. De otra manera, los usuarios podrían
experimentar problemas al utilizar su aplicación. Tenga en cuenta que
la primera sugerencia es la mejor, ya que las otras aún pueden ser
afectadas por rutas no estándar en el registro y en el site-packages
del usuario.

Distinto en la versión 3.6: Add "._pth" file support and removes
"applocal" option from "pyvenv.cfg".

Distinto en la versión 3.6: Add "python*XX*.zip" as a potential
landmark when directly adjacent to the executable.

Obsoleto desde la versión 3.6: Los módulos especificados en el
registro bajo "Modules" (no "PythonPath") pueden ser importados por
"importlib.machinery.WindowsRegistryFinder". Este buscador está
habilitado en Windows en la versión 3.6.0 y anteriores, pero es
posible que deba agregarse explícitamente a "sys.meta_path" en el
futuro.


4.9. Módulos adicionales
========================

Aunque Python pretende ser portátil entre todas las plataformas, hay
características que son exclusivas de Windows. Existen un par de
módulos, de la biblioteca estándar y externos, y fragmentos de código
para utilizar estas funciones.

Los módulos estándar específicos para Windows se encuentran
documentados en Servicios Específicos para MS Windows.


4.9.1. PyWin32
--------------

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

* Component Object Model (COM)

* Invocación de la API Win32

* Registro

* Registro de eventos

* Microsoft Foundation Classes (MFC) user interfaces

PythonWin es una aplicación MFC de muestra distribuida con PyWin32. Es
un IDE incrustable con depurador incorporado.

Ver también:

  Win32 How Do I...?
     por Tim Golden

  Python and COM
     por David y Paul Boddie


4.9.2. cx_Freeze
----------------

cx_Freeze envuelve scripts de Python en programas ejecutables de
Windows (archivos "***.exe").Cuando hayas hecho esto, puedes
distribuir tu aplicación sin requerir que tus usuarios instalen
Python.


4.10. Compilar Python en Windows
================================

Si desea compilar CPython usted mismo, lo primero que debe hacer es
obtener el source. Puede descargar la fuente de la última versión o
simplemente obtener un checkout nuevo.

El árbol fuente contiene una solución de compilación y archivos de
proyecto para Microsoft Visual Studio, que es el compilador que se usa
para compilar las versiones oficiales de Python. Estos archivos están
en el directorio "PCbuild".

Consulte "PCbuild/readme.txt" para obtener información general acerca
del proceso de compilación.

Para módulos de extensión, consulte Creación de extensiones C y C++ en
Windows.
