Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Traducido archivo reference/import.po #384

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 25 commits into from
Jul 25, 2020
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Apply suggestions from code review
Co-authored-by: Cristián Maureira-Fredes <[email protected]>
  • Loading branch information
Jighdan and cmaureir authored Jul 11, 2020
commit 4b5f6fcd0554aee7bb1ecb953530f413cb1031b7
34 changes: 17 additions & 17 deletions reference/import.po
Original file line number Diff line number Diff line change
Expand Up @@ -582,7 +582,7 @@ msgid ""
"qualified name of the module being imported, for example ``foo.bar.baz``. "
"The second argument is the path entries to use for the module search. For "
"top-level modules, the second argument is ``None``, but for submodules or "
"subpackages, the second argument is the value of the parent package`s "
"subpackages, the second argument is the value of the parent package's "
"``__path__`` attribute. If the appropriate ``__path__`` attribute cannot be "
"accessed, a :exc:`ModuleNotFoundError` is raised. The third argument is an "
"existing module object that will be the target of loading later. The import "
Expand Down Expand Up @@ -633,7 +633,7 @@ msgstr ""

#: ../Doc/reference/import.rst:318
msgid ""
"Python`s default :data:`sys.meta_path` has three meta path finders, one that "
"Python's default :data:`sys.meta_path` has three meta path finders, one that "
"knows how to import built-in modules, one that knows how to import frozen "
"modules, and one that knows how to import modules from an :term:`import "
"path` (i.e. the :term:`path based finder`)."
Expand Down Expand Up @@ -776,8 +776,8 @@ msgstr "Los cargadores deben cumplir los siguientes requisitos:"
#: ../Doc/reference/import.rst:412
msgid ""
"If the module is a Python module (as opposed to a built-in module or a "
"dynamically loaded extension), the loader should execute the module`s code "
"in the module`s global name space (``module.__dict__``)."
"dynamically loaded extension), the loader should execute the module's code "
"in the module's global name space (``module.__dict__``)."
msgstr ""
"Si el módulo es un módulo Python (a diferencia de un módulo integrado o una "
"extensión cargada dinámicamente), el cargador debe ejecutar el código del "
Expand Down Expand Up @@ -916,10 +916,10 @@ msgstr "Sub-modulos"
msgid ""
"When a submodule is loaded using any mechanism (e.g. ``importlib`` APIs, the "
"``import`` or ``import-from`` statements, or built-in ``__import__()``) a "
"binding is placed in the parent module`s namespace to the submodule object. "
"binding is placed in the parent module's namespace to the submodule object. "
"For example, if package ``spam`` has a submodule ``foo``, after importing "
"``spam.foo``, ``spam`` will have an attribute ``foo`` which is bound to the "
"submodule. Let`s say you have the following directory structure::"
"submodule. Let's say you have the following directory structure::"
msgstr ""
"Cuando se carga un submódulo mediante cualquier mecanismo (por ejemplo, API "
"``importlib``, las instrucciones ``import`` o ``import-from``, o "
Expand All @@ -943,10 +943,10 @@ msgstr ""

#: ../Doc/reference/import.rst:500
msgid ""
"Given Python`s familiar name binding rules this might seem surprising, but "
"it`s actually a fundamental feature of the import system. The invariant "
"holding is that if you have ``sys.modules[`spam`]`` and ``sys.modules[`spam."
"foo`]`` (as you would after the above import), the latter must appear as the "
"Given Python's familiar name binding rules this might seem surprising, but "
"it's actually a fundamental feature of the import system. The invariant "
"holding is that if you have ``sys.modules['spam']`` and ``sys.modules['spam."
"foo']`` (as you would after the above import), the latter must appear as the "
"``foo`` attribute of the former."
msgstr ""
"Dadas las reglas de enlace de nombres familiares de Python, esto puede "
Expand All @@ -964,7 +964,7 @@ msgstr "Especificaciones del módulo"
msgid ""
"The import machinery uses a variety of information about each module during "
"import, especially before loading. Most of the information is common to all "
"modules. The purpose of a module`s spec is to encapsulate this import-"
"modules. The purpose of a module's spec is to encapsulate this import-"
"related information on a per-module basis."
msgstr ""
"La maquinaria de importación utiliza una variedad de información sobre cada "
Expand All @@ -990,7 +990,7 @@ msgstr ""

#: ../Doc/reference/import.rst:520
msgid ""
"The module`s spec is exposed as the ``__spec__`` attribute on a module "
"The module's spec is exposed as the ``__spec__`` attribute on a module "
"object. See :class:`~importlib.machinery.ModuleSpec` for details on the "
"contents of the module spec."
msgstr ""
Expand All @@ -1005,7 +1005,7 @@ msgstr "Atributos de módulo relacionados con la importación"
#: ../Doc/reference/import.rst:531
msgid ""
"The import machinery fills in these attributes on each module object during "
"loading, based on the module`s spec, before the loader executes the module."
"loading, based on the module's spec, before the loader executes the module."
msgstr ""
"La máquina de importación rellena estos atributos en cada objeto de módulo "
"durante la carga, en función de las especificaciones del módulo, antes de "
Expand Down Expand Up @@ -1036,11 +1036,11 @@ msgstr ""

#: ../Doc/reference/import.rst:550
msgid ""
"The module`s ``__package__`` attribute must be set. Its value must be a "
"The module's ``__package__`` attribute must be set. Its value must be a "
"string, but it can be the same value as its ``__name__``. When the module "
"is a package, its ``__package__`` value should be set to its ``__name__``. "
"When the module is not a package, ``__package__`` should be set to the empty "
"string for top-level modules, or for submodules, to the parent package`s "
"string for top-level modules, or for submodules, to the parent package's "
"name. See :pep:`366` for further details."
msgstr ""
"Se debe establecer el atributo ``__package__`` del módulo. Su valor debe "
Expand Down Expand Up @@ -1174,7 +1174,7 @@ msgstr ""

#: ../Doc/reference/import.rst:620
msgid ""
"A package`s ``__path__`` attribute is used during imports of its "
"A package's ``__path__`` attribute is used during imports of its "
"subpackages. Within the import machinery, it functions much the same as :"
"data:`sys.path`, i.e. providing a list of locations to search for modules "
"during import. However, ``__path__`` is typically much more constrained "
Expand Down Expand Up @@ -1899,7 +1899,7 @@ msgstr "Consideraciones especiales para __main__"

#: ../Doc/reference/import.rst:967
msgid ""
"The :mod:`__main__` module is a special case relative to Python`s import "
"The :mod:`__main__` module is a special case relative to Python's import "
"system. As noted :ref:`elsewhere <programs>`, the ``__main__`` module is "
"directly initialized at interpreter startup, much like :mod:`sys` and :mod:"
"`builtins`. However, unlike those two, it doesn't strictly qualify as a "
Expand Down