# Copyright (C) 2001-2020, Python Software Foundation

# This file is distributed under the same license as the Python package.

# Maintained by the python-doc-es workteam.

# docs-es@python.org /

# https://mail.python.org/mailman3/lists/docs-es.python.org/

# Check https://github.com/python/python-docs-es/blob/3.8/TRANSLATORS to

# get the list of volunteers

#

msgid ""

msgstr ""

"Project-Id-Version: Python 3.8\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2026-02-26 18:44-0300\n"

"PO-Revision-Date: 2023-02-14 11:46-0300\n"

"Last-Translator: Carlos A. Crespo <lvccrespo@gmail.com>\n"

"Language: es\n"

"Language-Team: python-doc-es\n"

"Plural-Forms: nplurals=2; plural=(n != 1);\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=utf-8\n"

"Content-Transfer-Encoding: 8bit\n"

"Generated-By: Babel 2.18.0\n"

#: ../Doc/using/windows.rst:11

msgid "Using Python on Windows"

msgstr "Uso de Python en Windows"

#: ../Doc/using/windows.rst:15

msgid ""

"This document aims to give an overview of Windows-specific behaviour you "

"should know about when using Python on Microsoft Windows."

msgstr ""

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

#: ../Doc/using/windows.rst:18

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:26

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:32

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:37

msgid ""

"In general, we recommend that you create a :ref:`virtual environment <tut-"

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

msgstr ""

#: ../Doc/using/windows.rst:43

msgid ""

"If the ``python`` or ``py`` commands do not seem to be working, please see "

"the :ref:`Troubleshooting <pymanager-troubleshoot>` section below. There are "

"sometimes additional manual steps required to configure your PC."

msgstr ""

#: ../Doc/using/windows.rst:47

msgid ""

"Apart from using the Python install manager, Python can also be obtained as "

"NuGet packages. See :ref:`windows-nuget` below for more information on these "

"packages."

msgstr ""

#: ../Doc/using/windows.rst:51

msgid ""

"The embeddable distros are minimal packages of Python suitable for embedding "

"into larger applications. They can be installed using the Python install "

"manager. See :ref:`windows-embeddable` below for more information on these "

"packages."

msgstr ""

#: ../Doc/using/windows.rst:64

#, fuzzy

msgid "Python Install Manager"

msgstr "El instalador completo"

#: ../Doc/using/windows.rst:67

#, fuzzy

msgid "Installation"

msgstr "Pasos para la instalación"

#: ../Doc/using/windows.rst:69

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:73

msgid ""

"To install through the Store, simply click \"Install\". After it has "

"completed, open a terminal and type ``python`` to get started."

msgstr ""

#: ../Doc/using/windows.rst:76

msgid ""

"To install the file downloaded from python.org, either double-click and "

"select \"Install\", or run ``Add-AppxPackage <path to MSIX>`` in Windows "

"Powershell."

msgstr ""

#: ../Doc/using/windows.rst:79

msgid ""

"After installation, the ``python``, ``py``, and ``pymanager`` commands "

"should be available. If you have existing installations of Python, or you "

"have modified your :envvar:`PATH` variable, you may need to remove them or "

"undo the modifications. See :ref:`pymanager-troubleshoot` for more help with "

"fixing non-working commands."

msgstr ""

#: ../Doc/using/windows.rst:85

#, python-format

msgid ""

"When you first install a runtime, you will likely be prompted to add a "

"directory to your :envvar:`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 :"

"file:`%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."

msgstr ""

#: ../Doc/using/windows.rst:93

msgid ""

"Each Python runtime you install will have its own directory for scripts. "

"These also need to be added to :envvar:`PATH` if you want to use them."

msgstr ""

#: ../Doc/using/windows.rst:96

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:100

msgid ""

"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 :ref:`pymanager-advancedinstall` "

"below for more information."

msgstr ""

#: ../Doc/using/windows.rst:107

msgid "Basic Use"

msgstr ""

#: ../Doc/using/windows.rst:109

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:116

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:122

msgid ""

"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 install and launch your default "

"interpreter, while ``pymanager`` will display help (``pymanager exec ...`` "

"provides equivalent behaviour to ``py ...``)."

msgstr ""

#: ../Doc/using/windows.rst:131

msgid ""

"Each of these commands also has a windowed version that avoids creating a "

"console window. These are ``pyw``, ``pythonw`` and ``pymanagerw``. 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."

msgstr ""

#: ../Doc/using/windows.rst:137

msgid ""

"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):"

msgstr ""

#: ../Doc/using/windows.rst:140

msgid ""

"$> py\n"

"...\n"

"$> python my-script.py\n"

"...\n"

"$> py -m this\n"

"..."

msgstr ""

#: ../Doc/using/windows.rst:149

msgid ""

"The default runtime can be overridden with the :envvar:"

"`PYTHON_MANAGER_DEFAULT` environment variable, or a configuration file. See :"

"ref:`pymanager-config` for information about configuration settings."

msgstr ""

#: ../Doc/using/windows.rst:153

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:160

msgid ""

"$> py -V:3.14 ...\n"

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

msgstr ""

#: ../Doc/using/windows.rst:165

msgid ""

"Runtimes from other distributors may require the *company* to be included as "

"well. This should be separated from the tag by a slash, and may be a prefix. "

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

msgstr ""

#: ../Doc/using/windows.rst:171

msgid ""

"$> py -V:Distributor\\1.0 ...\n"

"$> py -V:distrib/ ..."

msgstr ""

#: ../Doc/using/windows.rst:176

msgid ""

"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 :ref:`pymanager-shebang` "

"for more information. When there is no shebang line, or it cannot be "

"resolved, the script will be launched with the default runtime."

msgstr ""

#: ../Doc/using/windows.rst:182

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:188

msgid ""

"When you launch either ``python`` or ``py`` but do not have any runtimes "

"installed, and the requested version is the default, it will be installed "

"automatically and then launched. Otherwise, the requested version will be "

"installed if automatic installation is configured (most likely by setting "

"``PYTHON_MANAGER_AUTOMATIC_INSTALL`` to ``true``), or if the ``py exec`` or "

"``pymanager exec`` forms of the command were used."

msgstr ""

#: ../Doc/using/windows.rst:197

msgid "Command Help"

msgstr ""

#: ../Doc/using/windows.rst:199

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:203

msgid ""

"$> py help\n"

"$> py help install\n"

"$> py install /?"

msgstr ""

#: ../Doc/using/windows.rst:210

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:216

msgid ""

"The ``--config=<PATH>`` option allows specifying a configuration file to "

"override multiple settings at once. See :ref:`pymanager-config` below for "

"more information about these files."

msgstr ""

#: ../Doc/using/windows.rst:222

msgid "Listing Runtimes"

msgstr ""

#: ../Doc/using/windows.rst:224

msgid ""

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

"[<TAG>...]"

msgstr ""

#: ../Doc/using/windows.rst:228

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:232

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:238

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:244

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:248

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:253

msgid "$> py list --online 3.14"

msgstr ""

#: ../Doc/using/windows.rst:257

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:263

#, fuzzy

msgid "Installing Runtimes"

msgstr "RC_INSTALLING"

#: ../Doc/using/windows.rst:265

msgid ""

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

"[<TAG>...]"

msgstr ""

#: ../Doc/using/windows.rst:269

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:273

msgid ""

"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 :ref:`pymanager-offline`."

msgstr ""

#: ../Doc/using/windows.rst:277

msgid ""

"Passing ``--force`` will ignore any cached files and remove any existing "

"install to replace it with the specified one."

msgstr ""

#: ../Doc/using/windows.rst:280

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:287

msgid ""

"Passing ``--dry-run`` will generate output and logs, but will not modify any "

"installs."

msgstr ""

#: ../Doc/using/windows.rst:290

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:294

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

msgstr ""

#: ../Doc/using/windows.rst:302

#, fuzzy

msgid "Offline Installs"

msgstr "Modificar una instalación"

#: ../Doc/using/windows.rst:304

msgid ""

"To perform offline installs of Python, you will need to first create an "

"offline index on a machine that has network access."

msgstr ""

#: ../Doc/using/windows.rst:307

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

msgstr ""

#: ../Doc/using/windows.rst:311

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:316

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

msgstr ""

#: ../Doc/using/windows.rst:320

msgid ""

"The Python install manager can be installed by downloading its installer and "

"moving it to another machine before installing."

msgstr ""

#: ../Doc/using/windows.rst:323

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:329

msgid ""

"In this way, Python runtimes can be installed and managed on a machine "

"without access to the internet."

msgstr ""

#: ../Doc/using/windows.rst:334

msgid "Uninstalling Runtimes"

msgstr ""

#: ../Doc/using/windows.rst:336

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

msgstr ""

#: ../Doc/using/windows.rst:340

msgid ""

"Runtimes may be removed using the ``py uninstall`` command. One or more tags "

"must be specified. Ranges are not supported here."

msgstr ""

#: ../Doc/using/windows.rst:343

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:345

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:351

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

msgstr ""

#: ../Doc/using/windows.rst:355

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:365

#, fuzzy

msgid "Configuration"

msgstr "Configuración de Python"

#: ../Doc/using/windows.rst:367

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:374

msgid ""

"This section will describe the defaults, but be aware that modified or "

"overridden installs may resolve settings differently."

msgstr ""

#: ../Doc/using/windows.rst:377

msgid ""

"A global configuration file may be configured by an administrator, and would "

"be read first. The user configuration file is stored at :file:`%AppData%\\"

"\\Python\\\\pymanager.json` (by default) 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)."

msgstr ""

#: ../Doc/using/windows.rst:384

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:392

msgid "Standard configuration options"

msgstr ""

#: ../Doc/using/windows.rst:396 ../Doc/using/windows.rst:676

msgid "Config Key"

msgstr ""

#: ../Doc/using/windows.rst:397

#, fuzzy

msgid "Environment Variable"

msgstr "Excurso: configurar variables de entorno"

#: ../Doc/using/windows.rst:398 ../Doc/using/windows.rst:677

#: ../Doc/using/windows.rst:1365 ../Doc/using/windows.rst:1385

#: ../Doc/using/windows.rst:1980

msgid "Description"

msgstr "Descripción"

#: ../Doc/using/windows.rst:400

#, fuzzy

msgid "``default_tag``"

msgstr "Predeterminado"

#: ../Doc/using/windows.rst:402

msgid ""

"The preferred default version to launch or install. By default, this is "

"interpreted as the most recent non-prerelease version from the CPython team."

msgstr ""

#: ../Doc/using/windows.rst:406

msgid "``default_platform``"

msgstr ""

#: ../Doc/using/windows.rst:407

msgid "``PYTHON_MANAGER_DEFAULT_PLATFORM``"

msgstr ""

#: ../Doc/using/windows.rst:408

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:414

msgid "``logs_dir``"

msgstr ""

#: ../Doc/using/windows.rst:415

#, fuzzy

msgid "``PYTHON_MANAGER_LOGS``"

msgstr "``python``"

#: ../Doc/using/windows.rst:416

msgid "The location where log files are written. By default, :file:`%TEMP%`."

msgstr ""

#: ../Doc/using/windows.rst:419

msgid "``automatic_install``"

msgstr ""

#: ../Doc/using/windows.rst:420

msgid "``PYTHON_MANAGER_AUTOMATIC_INSTALL``"

msgstr ""

#: ../Doc/using/windows.rst:421

msgid ""

"True to allow automatic installs when specifying a particular runtime to "

"launch. By default, true."

msgstr ""

#: ../Doc/using/windows.rst:425

msgid "``include_unmanaged``"

msgstr ""

#: ../Doc/using/windows.rst:426

msgid "``PYTHON_MANAGER_INCLUDE_UNMANAGED``"

msgstr ""

#: ../Doc/using/windows.rst:427

msgid ""

"True to allow listing and launching runtimes that were not installed by the "

"Python install manager, or false to exclude them. By default, true."

msgstr ""

#: ../Doc/using/windows.rst:431

msgid "``shebang_can_run_anything``"

msgstr ""

#: ../Doc/using/windows.rst:432

msgid "``PYTHON_MANAGER_SHEBANG_CAN_RUN_ANYTHING``"

msgstr ""

#: ../Doc/using/windows.rst:433

msgid ""

"True to allow shebangs in ``.py`` files to launch applications other than "

"Python runtimes, or false to prevent it. By default, true."

msgstr ""

#: ../Doc/using/windows.rst:437

msgid "``log_level``"

msgstr ""

#: ../Doc/using/windows.rst:438

msgid "``PYMANAGER_VERBOSE``, ``PYMANAGER_DEBUG``"

msgstr ""

#: ../Doc/using/windows.rst:439

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:445

msgid "``confirm``"

msgstr ""

#: ../Doc/using/windows.rst:446

msgid "``PYTHON_MANAGER_CONFIRM``"

msgstr ""

#: ../Doc/using/windows.rst:447

msgid ""

"True to confirm certain actions before taking them (such as uninstall), or "

"false to skip the confirmation. By default, true."

msgstr ""

#: ../Doc/using/windows.rst:451

msgid "``install.source``"

msgstr ""

#: ../Doc/using/windows.rst:452

msgid "``PYTHON_MANAGER_SOURCE_URL``"

msgstr ""

#: ../Doc/using/windows.rst:453

msgid "Override the index feed to obtain new installs from."

msgstr ""

#: ../Doc/using/windows.rst:455

msgid "``list.format``"

msgstr ""

#: ../Doc/using/windows.rst:456

msgid "``PYTHON_MANAGER_LIST_FORMAT``"

msgstr ""

#: ../Doc/using/windows.rst:457

msgid ""

"Specify the default format used by the ``py list`` command. By default, "

"``table``."

msgstr ""

#: ../Doc/using/windows.rst:460

#, python-brace-format

msgid ""

"Dotted names should be nested inside JSON objects, for example, ``list."

"format`` would be specified as ``{\"list\": {\"format\": \"table\"}}``."

msgstr ""

#: ../Doc/using/windows.rst:466

#, fuzzy

msgid "Shebang lines"

msgstr "Líneas shebang"

#: ../Doc/using/windows.rst:468

#, fuzzy

msgid ""

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

msgstr ""

"Si la primera línea de un script comienza con ``#!``, esta se denomina línea "

"\"shebang\". Linux y otros sistemas operativos tipo Unix soportan de forma "

"nativa este tipo de líneas y son comúnmente utilizadas en dichos sistemas "

"para indicar cómo debería ser ejecutado un script. Este lanzador permite que "

"la misma funcionalidad pueda ser utilizada con scripts de Python en Windows, "

"y los ejemplos anteriores demuestran su uso."

#: ../Doc/using/windows.rst:474

#, fuzzy

msgid ""

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

msgstr ""

"Para permitir que las líneas shebang de scripts de Python sean trasladables "

"entre Unix y Windows, este lanzador soporta varios comandos 'virtuales' para "

"especificar qué intérprete utilizar. Los comandos virtuales soportados son:"

#: ../Doc/using/windows.rst:478

#, fuzzy

msgid "``/usr/bin/env <ALIAS>``"

msgstr "``/usr/bin/env``"

#: ../Doc/using/windows.rst:479

#, fuzzy

msgid "``/usr/bin/env -S <ALIAS>``"

msgstr "``/usr/bin/env``"

#: ../Doc/using/windows.rst:480

#, fuzzy

msgid "``/usr/bin/<ALIAS>``"

msgstr "``/usr/bin/env``"

#: ../Doc/using/windows.rst:481

#, fuzzy

msgid "``/usr/local/bin/<ALIAS>``"

msgstr "``/usr/local/bin/python``"

#: ../Doc/using/windows.rst:482

msgid "``<ALIAS>``"

msgstr ""

#: ../Doc/using/windows.rst:484 ../Doc/using/windows.rst:1754

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

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

#: ../Doc/using/windows.rst:486 ../Doc/using/windows.rst:1756

#, fuzzy

msgid "#! /usr/bin/python"

msgstr "``/usr/bin/python``"

#: ../Doc/using/windows.rst:490 ../Doc/using/windows.rst:1760

#, fuzzy

msgid ""

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

msgstr ""

"La versión de Python predeterminada será ubicada y utilizada. Como muchos "

"scripts de Python escritos para funcionar en Unix tienen esta línea, debería "

"suceder que estos scripts pueden ser utilizados por el lanzador sin "

"modificaciones. Si está escribiendo un nuevo script en Windows que espera "

"que sea útil en Unix, debería utilizar una de las líneas shebang que "

"comienza con ``/usr``."

#: ../Doc/using/windows.rst:496

msgid ""

"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 :envvar:`PATH` "

"environment variable) can be used in a shebang, even if it is not on your :"

"envvar:`PATH`. This allows the use of shebangs like ``/usr/bin/python3.12`` "

"to select a particular runtime."

msgstr ""

#: ../Doc/using/windows.rst:502

msgid ""

"If no runtimes are installed, or if automatic installation is enabled, the "

"requested runtime will be installed if necessary. See :ref:`pymanager-"

"config` for information about configuration settings."

msgstr ""

#: ../Doc/using/windows.rst:506

msgid ""

"The ``/usr/bin/env`` form of shebang line will also search the :envvar:"

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

msgstr ""

#: ../Doc/using/windows.rst:513

#, fuzzy

msgid ""

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

msgstr ""

"Cualquier comando que no se encuentre en el archivo .INI se trata como rutas "

"ejecutables de **Windows** que son absolutas o relativas al directorio que "

"contiene el archivo de script. Esto es una comodidad para los scripts solo "

"para Windows, como aquellos generados por un instalador, ya que el "

"comportamiento no es compatible con los shells al estilo Unix. Estas rutas "

"pueden estar entre comillas y pueden incluir varios argumentos, tras los "

"cuales se añadirá la ruta al script y cualquier argumento adicional."

#: ../Doc/using/windows.rst:524

msgid ""

"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 keeping the legacy launcher. It may be "

"`downloaded independently <https://www.python.org/ftp/python/3.13.1/win32/"

"launcher.msi>`_ and installed on its own. The legacy launcher's ``py`` "

"command will override PyManager's one, and you will need to use "

"``pymanager`` commands for installing and uninstalling."

msgstr ""

#: ../Doc/using/windows.rst:545

#, fuzzy

msgid "Advanced Installation"

msgstr "Pasos para la instalación"

#: ../Doc/using/windows.rst:547

msgid ""

"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 :envvar:`PATH` environment variable to "

"include this install location, but be sure to validate this on your "

"configuration."

msgstr ""

#: ../Doc/using/windows.rst:556

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:559

msgid ""

"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 :ref:`pymanager-offline` and :ref:`pymanager-"

"admin-config` for information on handling these scenarios."

msgstr ""

#: ../Doc/using/windows.rst:564

msgid ""

"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 :envvar:`PATH`, the registry, or the Start "

"menu."

msgstr ""

#: ../Doc/using/windows.rst:570

#, python-format

msgid ""

"When the MSIX is installed, but commands are not available in the :envvar:"

"`PATH` environment variable, they can be found under :file:`%LocalAppData%\\"

"\\Microsoft\\\\WindowsApps\\\\PythonSoftwareFoundation."

"PythonManager_3847v3x7pw1km` or :file:`%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."

msgstr ""

#: ../Doc/using/windows.rst:579

msgid ""

"To programmatically install the Python install manager, it is easiest to use "

"WinGet, which is included with all supported versions of Windows:"

msgstr ""

#: ../Doc/using/windows.rst:582

msgid ""

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

"interactivity\n"

"\n"

"# Optionally run the configuration checker and accept all changes\n"

"$> py install --configure -y"

msgstr ""

#: ../Doc/using/windows.rst:589

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:595

msgid ""

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

"agreements --accept-source-agreements"

msgstr ""

#: ../Doc/using/windows.rst:599

msgid ""

"To programmatically install or uninstall an MSIX using only PowerShell, the "

"`Add-AppxPackage`_ and `Remove-AppxPackage`_ PowerShell cmdlets are "

"recommended:"

msgstr ""

#: ../Doc/using/windows.rst:602

msgid ""

"$> Add-AppxPackage C:\\Downloads\\python-manager-25.0.msix\n"

"...\n"

"$> Get-AppxPackage PythonSoftwareFoundation.PythonManager | Remove-"

"AppxPackage"

msgstr ""

#: ../Doc/using/windows.rst:608

msgid ""

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

msgstr ""

#: ../Doc/using/windows.rst:613

msgid ""

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

"pymanager/pymanager.appinstaller"

msgstr ""

#: ../Doc/using/windows.rst:617

msgid ""

"Other tools and APIs may also be used to provision an MSIX package for all "