8000 Finalizando c-api/type by cmaureir · Pull Request #1729 · python/python-docs-es · GitHub
[go: up one dir, main page]
Skip to content

Finalizando c-api/type #1729

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.

Sign up for GitHub

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 2 commits into from
Dec 15, 2021
Merged

Finalizando c-api/type #1729

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4ab48b5
Finalizando c-api/type
cmaureir Dec 14, 2021
754ed05
Apply suggestions from code review
cmaureir Dec 15, 2021
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
26 changes: 20 additions & 6 deletions c-api/type.po
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,12 +13,12 @@ msgstr ""
"POT-Creation-Date: 2021-10-16 21:42+0200\n"
"PO-Revision-Date: 2021-08-02 01:37+0200\n"
"Last-Translator: Cristián Maureira-Fredes <cmaureirafredes@gmail.com>\n"
"Language: es\n"
"Language-Team: python-doc-es\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
"Language: es\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"
"Generated-By: Babel 2.9.1\n"

#: ../Doc/c-api/type.rst:6
8000 Expand Down Expand Up @@ -165,6 +165,13 @@ msgid ""
"in its flags then it **must** implement the GC protocol itself by at least "
"implementing the :c:member:`~PyTypeObject.tp_traverse` handle."
msgstr ""
"Si algunas de las clases base implementan el protocolo GC y el tipo "
"proporcionado no incluye el :const:`Py_TPFLAGS_HAVE_GC` en sus banderas, "
"entonces el protocolo GC se implementará automáticamente desde sus padres. "
"Por el contrario, si el tipo que se está creando incluye :const:"
"`Py_TPFLAGS_HAVE_GC` en sus banderas, entonces **debe** implementar el "
"protocolo GC por sí mismo al implementar al menos el identificador :c:member:"
"`~PyTypeObject.tp_traverse`."

#: ../Doc/c-api/type.rst:111
msgid ""
Expand All @@ -190,6 +197,8 @@ msgid ""
":c:func:`PyType_GetSlot` can now accept all types. Previously, it was "
"limited to :ref:`heap types <heap-types>`."
msgstr ""
":c:func:`PyType_GetSlot` ahora puede aceptar todos los tipos. Anteriormente, "
"estaba limitado a :ref:`heap types <heap-types>`."

#: ../Doc/c-api/type.rst:127
msgid ""
Expand Down Expand Up @@ -255,12 +264,11 @@ msgstr ""
"types <heap-types>`."

#: ../Doc/c-api/type.rst:165
#, fuzzy
msgid ""
"Creates and returns a :ref:`heap type <heap-types>` from the *spec* (:const:"
"`Py_TPFLAGS_HEAPTYPE`)."
msgstr ""
"Crea y retorna un objeto montículo (*heap*) a partir de *spec* (:const:"
"Crea y retorna un :ref:`tipo heap <heap-types>` a partir del *spec* (:const:"
"`Py_TPFLAGS_HEAPTYPE`)."
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Objeto montículo como en el origal? No se cuál es el término que se usa más extendidamente en la documentación, si no dejarlo como está igual está bien supongo

Copy link
Collaborator Author
@cmaureir cmaureir Dec 15, 2021 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

uuh...creo que al final dejamos "tipo heap", sin traducirlo. lo cambio a tipo heap de todas formas.


#: ../Doc/c-api/type.rst:168
Expand All @@ -271,9 +279,13 @@ msgid ""
"*Py_tp_base* slot is used instead. If that also is ``NULL``, the new type "
"derives from :class:`object`."
msgstr ""
"El argumento *bases* se puede utilizar para especificar clases base; puede "
"ser solo una clase o una tupla de clases. Si *bases* es ``NULL``, en su "
"lugar se utiliza la ranura *Py_tp_bases*. Si esa también es ``NULL``, se usa "
"la ranura *Py_tp_base* en su lugar. Si también es ``NULL``, el nuevo tipo se "
"deriva de :class:`object`."

#: ../Doc/c-api/type.rst:174
#, fuzzy
msgid ""
"The *module* argument can be used to record the module in which the new "
"class is defined. It must be a module object or ``NULL``. If not ``NULL``, "
Expand All @@ -296,6 +308,8 @@ msgid ""
"The function now accepts a single class as the *bases* argument and ``NULL`` "
"as the ``tp_doc`` slot."
msgstr ""
"La función ahora acepta una sola clase como argumento *bases* y ``NULL`` "
"como ranura ``tp_doc``."

#: ../Doc/c-api/type.rst:192
msgid "Equivalent to ``PyType_FromModuleAndSpec(NULL, spec, bases)``."
Expand Down Expand Up @@ -479,7 +493,7 @@ msgstr ""

#: ../Doc/c-api/type.rst:282
msgid "Slots other than ``Py_tp_doc`` may not be ``NULL``."
msgstr ""
msgstr "Las ranuras que no sean ``Py_tp_doc`` pueden no ser ``NULL``."

#~ msgid ":c:member:`~PyTypeObject.tp_print`"
#~ msgstr ":c:member:`~PyTypeObject.tp_print`"
Expand Down
0