introduction.po

# 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: 2024-11-27 23:58+0100\n"
"Last-Translator: Xavi Francisco <xavi@srxavi.me>\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/reference/introduction.rst:6
msgid "Introduction"
msgstr "Introducción"

#: ../Doc/reference/introduction.rst:8
msgid ""
"This reference manual describes the Python programming language. It is not "
"intended as a tutorial."
msgstr ""
"Este manual de referencia describe el lenguaje de programación Python. No "
"pretende ser un tutorial."

#: ../Doc/reference/introduction.rst:11
msgid ""
"While I am trying to be as precise as possible, I chose to use English "
"rather than formal specifications for everything except syntax and lexical "
"analysis. This should make the document more understandable to the average "
"reader, but will leave room for ambiguities. Consequently, if you were "
"coming from Mars and tried to re-implement Python from this document alone, "
"you might have to guess things and in fact you would probably end up "
"implementing quite a different language. On the other hand, if you are using "
"Python and wonder what the precise rules about a particular area of the "
"language are, you should definitely be able to find them here. If you would "
"like to see a more formal definition of the language, maybe you could "
"volunteer your time --- or invent a cloning machine :-)."
msgstr ""
"Aunque intento ser lo más preciso posible, he optado por utilizar el Español "
"(N. de T.: del original en inglés \\\"I chose to use English\\\")\" en lugar "
"de especificaciones formales para todo, excepto para la sintaxis y el "
"análisis léxico. Esto debería hacer el documento más comprensible para el "
"lector medio, pero dejará espacio para ambigüedades. En consecuencia, si "
"vienes de Marte y tratas de re implementar Python sólo a partir de este "
"documento, puede que tengas que adivinar cosas y, de hecho, probablemente "
"acabarías implementando un lenguaje bastante diferente. Por otro lado, si "
"estás usando Python y te preguntas cuáles son las reglas precisas sobre un "
"área particular del lenguaje, deberías poder encontrarlas aquí. Si te "
"gustaría ver una definición más formal del lenguaje, quizás podrías ofrecer "
"tu tiempo --- o inventar una máquina clonadora :-)."

#: ../Doc/reference/introduction.rst:23
msgid ""
"It is dangerous to add too many implementation details to a language "
"reference document --- the implementation may change, and other "
"implementations of the same language may work differently.  On the other "
"hand, CPython is the one Python implementation in widespread use (although "
"alternate implementations continue to gain support), and its particular "
"quirks are sometimes worth being mentioned, especially where the "
"implementation imposes additional limitations. Therefore, you'll find short "
"\"implementation notes\" sprinkled throughout the text."
msgstr ""
"Es peligroso añadir muchos detalles de implementación en un documento de "
"referencia: la implementación puede cambiar y otras implementaciones del "
"lenguaje pueden funcionar de forma diferente. Por otro lado, CPython es la "
"implementación de Python más usada (aunque implementaciones alternativas "
"están ganando soporte), y es importante mencionar sus detalles particulares "
"especialmente donde la implementación  impone limitaciones adicionales. Por "
"lo tanto, encontrarás pequeñas \"notas sobre la implementación\" repartidas "
"por todo el texto."

#: ../Doc/reference/introduction.rst:32
msgid ""
"Every Python implementation comes with a number of built-in and standard "
"modules.  These are documented in :ref:`library-index`.  A few built-in "
"modules are mentioned when they interact in a significant way with the "
"language definition."
msgstr ""
"Cada implementación de Python viene con un número de módulos estándar "
"incorporados. Éstos están documentados en :ref:`library-index`. Unos pocos "
"de estos módulos son citados cuando interactúan de forma significativa con "
"la definición del lenguaje."

#: ../Doc/reference/introduction.rst:41
msgid "Alternate Implementations"
msgstr "Implementaciones alternativas"

#: ../Doc/reference/introduction.rst:43
msgid ""
"Though there is one Python implementation which is by far the most popular, "
"there are some alternate implementations which are of particular interest to "
"different audiences."
msgstr ""
"Aunque hay una implementación de Python que es, de lejos, la más popular, "
"hay otras implementaciones alternativas que pueden ser de particular interés "
"para diferentes audiencias."

#: ../Doc/reference/introduction.rst:47
msgid "Known implementations include:"
msgstr "Las implementaciones conocidas incluyen:"

#: ../Doc/reference/introduction.rst:49
msgid "CPython"
msgstr "CPython"

#: ../Doc/reference/introduction.rst:50
msgid ""
"This is the original and most-maintained implementation of Python, written "
"in C. New language features generally appear here first."
msgstr ""
"Es la implementación original, y la más mantenida, de Python y está escrita "
"en C. Las nuevas características del lenguaje normalmente aparecen primero "
"aquí."

#: ../Doc/reference/introduction.rst:53
msgid "Jython"
msgstr "Jython"

#: ../Doc/reference/introduction.rst:54
msgid ""
"Python implemented in Java.  This implementation can be used as a scripting "
"language for Java applications, or can be used to create applications using "
"the Java class libraries.  It is also often used to create tests for Java "
"libraries. More information can be found at `the Jython website <https://www."
"jython.org/>`_."
msgstr ""
"Python implementado en Java. Esta implementación puede utilizarse como "
"lenguaje de scripting para aplicaciones Java, o puede utilizarse para crear "
"aplicaciones utilizando las bibliotecas de clases Java.  También se utiliza "
"a menudo para crear pruebas para bibliotecas Java. Puede encontrar más "
"información en `the Jython website <https://www.jython.org/>`_."

#: ../Doc/reference/introduction.rst:59
msgid "Python for .NET"
msgstr "Python para .NET"

#: ../Doc/reference/introduction.rst:60
msgid ""
"This implementation actually uses the CPython implementation, but is a "
"managed .NET application and makes .NET libraries available.  It was created "
"by Brian Lloyd.  For more information, see the `Python for .NET home page "
"<https://pythonnet.github.io/>`_."
msgstr ""
"Esta implementación, de hecho, usa la implementación CPython, pero es una "
"aplicación .NET gestionada y usa librerías .NET. Ha sido creada por Brian "
"Lloyd. Para más información ir al `sitio web de Python for .NET <https://"
"pythonnet.github.io/>`_."

#: ../Doc/reference/introduction.rst:65
msgid "IronPython"
msgstr "IronPython"

#: ../Doc/reference/introduction.rst:66
msgid ""
"An alternate Python for .NET.  Unlike Python.NET, this is a complete Python "
"implementation that generates IL, and compiles Python code directly to .NET "
"assemblies.  It was created by Jim Hugunin, the original creator of Jython.  "
"For more information, see `the IronPython website <https://ironpython.net/"
">`_."
msgstr ""
"Una alternativa de Python para .NET.  A diferencia de Python.NET, esta es "
"una implementación completa de Python que genera IL, y compila código Python "
"directamente a ensamblados .NET.  Fue creado por Jim Hugunin, el creador "
"original de Jython. Para más información, consulte `el sitio web de "
"IronPython <https://ironpython.net/>`_."

#: ../Doc/reference/introduction.rst:71
msgid "PyPy"
msgstr "PyPy"

#: ../Doc/reference/introduction.rst:72
msgid ""
"An implementation of Python written completely in Python. It supports "
"several advanced features not found in other implementations like stackless "
"support and a Just in Time compiler. One of the goals of the project is to "
"encourage experimentation with the language itself by making it easier to "
"modify the interpreter (since it is written in Python).  Additional "
"information is available on `the PyPy project's home page <https://pypy.org/"
">`_."
msgstr ""
"Una implementación de Python escrita completamente en Python. Soporta varias "
"características avanzadas que no se encuentran en otras implementaciones "
"como compatibilidad stackless y un compilador Just in Time. Uno de los "
"objetivos del proyecto es fomentar la experimentación con el propio lenguaje "
"facilitando la modificación del intérprete (ya que está escrito en Python). "
"Puede encontrar más información en la página principal del proyecto 'PyPy "
"<https://www.pypy.org/>_'."

#: ../Doc/reference/introduction.rst:79
msgid ""
"Each of these implementations varies in some way from the language as "
"documented in this manual, or introduces specific information beyond what's "
"covered in the standard Python documentation.  Please refer to the "
"implementation-specific documentation to determine what else you need to "
"know about the specific implementation you're using."
msgstr ""
"Cada una de estas implementaciones varía de una forma u otra del lenguaje "
"tal y como está documentado en este manual, o introduce información "
"específica más allá de lo cubierto por la documentación estándar de Python. "
"Por favor, consulte la documentación específica de cada implementación para "
"saber qué tienes que saber acerca de la implementación específica que uses."

#: ../Doc/reference/introduction.rst:89
msgid "Notation"
msgstr "Notación"

#: ../Doc/reference/introduction.rst:93
#, fuzzy, python-format
msgid ""
"The descriptions of lexical analysis and syntax use a grammar notation that "
"is a mixture of `EBNF <https://en.wikipedia.org/wiki/"
"Extended_Backus%E2%80%93Naur_form>`_ and `PEG <https://en.wikipedia.org/wiki/"
"Parsing_expression_grammar>`_. For example:"
msgstr ""
"Las descripciones del análisis léxico y sintáctico usan una notación "
"gramatical BNF modificada `Backus–Naur form (BNF) <https://es.wikipedia.org/"
"wiki/Notación_de_Backus-Naur>`_. De tal forma, utilizan el siguiente estilo "
"de definición:"

#: ../Doc/reference/introduction.rst:106
#, fuzzy
msgid ""
"In this example, the first line says that a ``name`` is a ``letter`` "
"followed by a sequence of zero or more ``letter``\\ s, ``digit``\\ s, and "
"underscores. A ``letter`` in turn is any of the single characters ``'a'`` "
"through ``'z'`` and ``A`` through ``Z``; a ``digit`` is a single character "
"from ``0`` to ``9``."
msgstr ""
"La primera línea dice que un ``name`` es una ``lc_letter`` seguida de una "
"secuencia de cero o más ``lc_letter``\\s y guiones bajos. Una ``lc_letter`` "
"es, a su vez, cualquiera de los caracteres de la ``'a'`` a la ``'z'``. (Esta "
"regla se cumple realmente para los nombres definidos en las reglas léxicas y "
"gramaticales en este documento.)"

#: ../Doc/reference/introduction.rst:112
msgid ""
"Each rule begins with a name (which identifies the rule that's being "
"defined) followed by a colon, ``:``. The definition to the right of the "
"colon uses the following syntax elements:"
msgstr ""

#: ../Doc/reference/introduction.rst:116
msgid ""
"``name``: A name refers to another rule. Where possible, it is a link to the "
"rule's definition."
msgstr ""

#: ../Doc/reference/introduction.rst:119
msgid ""
"``TOKEN``: An uppercase name refers to a :term:`token`. For the purposes of "
"grammar definitions, tokens are the same as rules."
msgstr ""

#: ../Doc/reference/introduction.rst:122
msgid ""
"``\"text\"``, ``'text'``: Text in single or double quotes must match "
"literally (without the quotes). The type of quote is chosen according to the "
"meaning of ``text``:"
msgstr ""

#: ../Doc/reference/introduction.rst:126
msgid "``'if'``: A name in single quotes denotes a :ref:`keyword <keywords>`."
msgstr ""

#: ../Doc/reference/introduction.rst:127
msgid ""
"``\"case\"``: A name in double quotes denotes a :ref:`soft-keyword <soft-"
"keywords>`."
msgstr ""

#: ../Doc/reference/introduction.rst:129
msgid ""
"``'@'``: A non-letter symbol in single quotes denotes an :py:data:`~token."
"OP` token, that is, a :ref:`delimiter <delimiters>` or :ref:`operator "
"<operators>`."
msgstr ""

#: ../Doc/reference/introduction.rst:133
msgid ""
"``e1 e2``: Items separated only by whitespace denote a sequence. Here, "
"``e1`` must be followed by ``e2``."
msgstr ""

#: ../Doc/reference/introduction.rst:135
msgid ""
"``e1 | e2``: A vertical bar is used to separate alternatives. It denotes "
"PEG's \"ordered choice\": if ``e1`` matches, ``e2`` is not considered. In "
"traditional PEG grammars, this is written as a slash, ``/``, rather than a "
"vertical bar. See :pep:`617` for more background and details."
msgstr ""

#: ../Doc/reference/introduction.rst:141
msgid "``e*``: A star means zero or more repetitions of the preceding item."
msgstr ""

#: ../Doc/reference/introduction.rst:142
msgid "``e+``: Likewise, a plus means one or more repetitions."
msgstr ""

#: ../Doc/reference/introduction.rst:143
msgid ""
"``[e]``: A phrase enclosed in square brackets means zero or one occurrences. "
"In other words, the enclosed phrase is optional."
msgstr ""

#: ../Doc/reference/introduction.rst:145
msgid ""
"``e?``: A question mark has exactly the same meaning as square brackets: the "
"preceding item is optional."
msgstr ""

#: ../Doc/reference/introduction.rst:147
msgid "``(e)``: Parentheses are used for grouping."
msgstr ""

#: ../Doc/reference/introduction.rst:149
msgid ""
"The following notation is only used in :ref:`lexical definitions <notation-"
"lexical-vs-syntactic>`."
msgstr ""

#: ../Doc/reference/introduction.rst:152
msgid ""
"``\"a\"...\"z\"``: Two literal characters separated by three dots mean a "
"choice of any single character in the given (inclusive) range of ASCII "
"characters."
msgstr ""

#: ../Doc/reference/introduction.rst:154
msgid ""
"``<...>``: A phrase between angular brackets gives an informal description "
"of the matched symbol (for example, ``<any ASCII character except \"\\"
"\">``), or an abbreviation that is defined in nearby text (for example, "
"``<Lu>``)."
msgstr ""

#: ../Doc/reference/introduction.rst:160
msgid ""
"Some definitions also use *lookaheads*, which indicate that an element must "
"(or must not) match at a given position, but without consuming any input:"
msgstr ""

#: ../Doc/reference/introduction.rst:163
msgid "``&e``: a positive lookahead (that is, ``e`` is required to match)"
msgstr ""

#: ../Doc/reference/introduction.rst:164
msgid ""
"``!e``: a negative lookahead (that is, ``e`` is required *not* to match)"
msgstr ""

#: ../Doc/reference/introduction.rst:166
msgid ""
"The unary operators (``*``, ``+``, ``?``) bind as tightly as possible; the "
"vertical bar (``|``) binds most loosely."
msgstr ""

#: ../Doc/reference/introduction.rst:169
msgid "White space is only meaningful to separate tokens."
msgstr ""

#: ../Doc/reference/introduction.rst:171
msgid ""
"Rules are normally contained on a single line, but rules that are too long "
"may be wrapped:"
msgstr ""

#: ../Doc/reference/introduction.rst:180
msgid ""
"Alternatively, rules may be formatted with the first line ending at the "
"colon, and each alternative beginning with a vertical bar on a new line. For "
"example:"
msgstr ""

#: ../Doc/reference/introduction.rst:195
msgid "This does *not* mean that there is an empty first alternative."
msgstr ""

#: ../Doc/reference/introduction.rst:202
#, fuzzy
msgid "Lexical and Syntactic definitions"
msgstr "lexical definitions"

#: ../Doc/reference/introduction.rst:204
msgid ""
"There is some difference between *lexical* and *syntactic* analysis: the :"
"term:`lexical analyzer` operates on the individual characters of the input "
"source, while the *parser* (syntactic analyzer) operates on the stream of :"
"term:`tokens <token>` generated by the lexical analysis. However, in some "
"cases the exact boundary between the two phases is a CPython implementation "
"detail."
msgstr ""

#: ../Doc/reference/introduction.rst:211
msgid ""
"The practical difference between the two is that in *lexical* definitions, "
"all whitespace is significant. The lexical analyzer :ref:`discards "
"<whitespace>` all whitespace that is not converted to tokens like :data:"
"`token.INDENT` or :data:`~token.NEWLINE`. *Syntactic* definitions then use "
"these tokens, rather than source characters."
msgstr ""

#: ../Doc/reference/introduction.rst:217
msgid ""
"This documentation uses the same BNF grammar for both styles of definitions. "
"All uses of BNF in the next chapter (:ref:`lexical`) are lexical "
"definitions; uses in subsequent chapters are syntactic definitions."
msgstr ""

#: ../Doc/reference/introduction.rst:91
msgid "BNF"
msgstr "BNF"

#: ../Doc/reference/introduction.rst:91
msgid "grammar"
msgstr "grammar"

#: ../Doc/reference/introduction.rst:91
msgid "syntax"
msgstr "syntax"

#: ../Doc/reference/introduction.rst:91
msgid "notation"
msgstr "notation"

#: ../Doc/reference/introduction.rst:197
msgid "lexical definitions"
msgstr "lexical definitions"

#~ msgid ""
#~ "Each rule begins with a name (which is the name defined by the rule) and "
#~ "``::=``.  A vertical bar (``|``) is used to separate alternatives; it is "
#~ "the least binding operator in this notation.  A star (``*``) means zero "
#~ "or more repetitions of the preceding item; likewise, a plus (``+``) means "
#~ "one or more repetitions, and a phrase enclosed in square brackets "
#~ "(``[ ]``) means zero or one occurrences (in other words, the enclosed "
#~ "phrase is optional).  The ``*`` and ``+`` operators bind as tightly as "
#~ "possible; parentheses are used for grouping.  Literal strings are "
#~ "enclosed in quotes.  White space is only meaningful to separate tokens. "
#~ "Rules are normally contained on a single line; rules with many "
#~ "alternatives may be formatted alternatively with each line after the "
#~ "first beginning with a vertical bar."
#~ msgstr ""
#~ "Cada regla empieza con un nombre (que es el nombre definido por la regla) "
#~ "y ``::=``. Una barra vertical (``|``) se usa para separar alternativas; "
#~ "es el operador menos vinculante en esta notación. Un asterisco (``*``) "
#~ "significa cero o más repeticiones del elemento anterior; del mismo modo, "
#~ "un signo más (``+``) significa una o más repeticiones, y una frase entre "
#~ "corchetes (``[]``) significa cero o una ocurrencia (en otras palabras, la "
#~ "frase adjunta es opcional). Los operadores ``*`` y ``+`` se vinculan lo "
#~ "más firmemente posible; los paréntesis se usan para agrupar. Las cadenas "
#~ "de caracteres literales están entre comillas. El espacio en blanco sólo "
#~ "es útil para separar tokens. Las reglas normalmente están contenidas en "
#~ "una sola línea; las reglas con varias alternativas se pueden formatear, "
#~ "de forma alternativa, con una barra vertical con cada línea después del "
#~ "primer comienzo."

#~ msgid ""
#~ "In lexical definitions (as the example above), two more conventions are "
#~ "used: Two literal characters separated by three dots mean a choice of any "
#~ "single character in the given (inclusive) range of ASCII characters.  A "
#~ "phrase between angular brackets (``<...>``) gives an informal description "
#~ "of the symbol defined; e.g., this could be used to describe the notion of "
#~ "'control character' if needed."
#~ msgstr ""
#~ "En las definiciones léxicas (como el ejemplo anterior), se utilizan dos "
#~ "convenciones más: Dos caracteres literales separados por tres puntos "
#~ "significan que se puede elegir cualquier carácter de la gama dada "
#~ "(inclusiva) de caracteres ASCII. Una frase entre corchetes angulares "
#~ "(``<...>``) ofrece una descripción informal del símbolo definido; por "
#~ "ejemplo, podría utilizarse para describir la noción de \"carácter de "
#~ "control\" si fuera necesario."

#~ msgid ""
#~ "Even though the notation used is almost the same, there is a big "
#~ "difference between the meaning of lexical and syntactic definitions: a "
#~ "lexical definition operates on the individual characters of the input "
#~ "source, while a syntax definition operates on the stream of tokens "
#~ "generated by the lexical analysis. All uses of BNF in the next chapter "
#~ "(\"Lexical Analysis\") are lexical definitions; uses in subsequent "
#~ "chapters are syntactic definitions."
#~ msgstr ""
#~ "Aunque la notación utilizada es casi la misma, hay una gran diferencia "
#~ "entre el significado de las definiciones léxicas y sintácticas: una "
#~ "definición léxica opera sobre los caracteres individuales de la fuente de "
#~ "entrada, mientras que una definición sintáctica opera sobre el flujo de "
#~ "tokens generado por el análisis léxico. Todos los usos de BNF en el "
#~ "próximo capítulo (\\\"Análisis léxico\\\") son definiciones léxicas; los "
#~ "usos en los capítulos siguientes son definiciones sintácticas."

#~ msgid "ASCII"
#~ msgstr "ASCII"