@@ -61,13 +61,12 @@ msgstr ""
6161
6262#: ../Doc/c-api/call.rst:25
6363msgid ""
64- "This convention is not only used by "
65- "*tp_call*: :c:member:`~PyTypeObject.tp_new` "
66- "and :c:member:`~PyTypeObject.tp_init` also pass arguments this way."
64+ "This convention is not only used by *tp_call*: :c:member:`~PyTypeObject."
65+ "tp_new` and :c:member:`~PyTypeObject.tp_init` also pass arguments this way."
6766msgstr ""
68- "Esta convención no solo es utilizada por "
69- "*tp_call*: :c:member:`~PyTypeObject.tp_new` "
70- "y :c:member:`~PyTypeObject.tp_init` también pasan argumentos de esta manera."
67+ "Esta convención no solo es utilizada por*tp_call*: :c:member:`~PyTypeObject. "
68+ "tp_new` y :c:member:`~PyTypeObject.tp_init` también pasan argumentos de esta "
69+ "manera."
7170
7271#: ../Doc/c-api/call.rst:29
7372#, fuzzy
@@ -94,13 +93,12 @@ msgstr ""
9493msgid ""
9594"As rule of thumb, CPython will prefer the vectorcall for internal calls if "
9695"the callable supports it. However, this is not a hard rule. Additionally, "
97- "some third-party extensions use *tp_call* directly (rather than "
98- "using :c:func:`PyObject_Call`). Therefore, a class supporting vectorcall "
99- "must also implement :c:member:`~PyTypeObject.tp_call`. Moreover, the "
100- "callable must behave the same regardless of which protocol is used. The "
101- "recommended way to achieve this is by "
102- "setting :c:member:`~PyTypeObject.tp_call` to :c:func:`PyVectorcall_Call`. "
103- "This bears repeating:"
96+ "some third-party extensions use *tp_call* directly (rather than using :c:"
97+ "func:`PyObject_Call`). Therefore, a class supporting vectorcall must also "
98+ "implement :c:member:`~PyTypeObject.tp_call`. Moreover, the callable must "
99+ "behave the same regardless of which protocol is used. The recommended way to "
100+ "achieve this is by setting :c:member:`~PyTypeObject.tp_call` to :c:func:"
101+ "`PyVectorcall_Call`. This bears repeating:"
104102msgstr ""
105103"Como regla general, CPython preferirá el vectorcall para llamadas internas "
106104"si el invocable lo admite. Sin embargo, esta no es una regla estricta. "
@@ -109,16 +107,16 @@ msgstr ""
109107"vectorcall también debe implementar :c:member:`~PyTypeObject.tp_call`. "
110108"Además, el invocable debe comportarse de la misma manera independientemente "
111109"del protocolo que se utilice. La forma recomendada de lograr esto es "
112- "configurando :c:member:`~PyTypeObject.tp_call` "
113- "en :c:func: `PyVectorcall_Call`. Vale la pena repetirlo:"
110+ "configurando :c:member:`~PyTypeObject.tp_call`en :c:func: "
111+ "`PyVectorcall_Call`. Vale la pena repetirlo:"
114112
115113#: ../Doc/c-api/call.rst:57
116114msgid ""
117- "A class supporting vectorcall **must** also "
118- "implement :c:member: `~PyTypeObject.tp_call` with the same semantics."
115+ "A class supporting vectorcall **must** alsoimplement :c:member: "
116+ "`~PyTypeObject.tp_call` with the same semantics."
119117msgstr ""
120- "Una clase que admita vectorcall **debe** también "
121- "implementar :c:member: `~PyTypeObject.tp_call` con la misma semántica."
118+ "Una clase que admita vectorcall **debe** tambiénimplementar :c:member: "
119+ "`~PyTypeObject.tp_call` con la misma semántica."
122120
123121#: ../Doc/c-api/call.rst:62
124122msgid ""
@@ -145,17 +143,17 @@ msgstr ""
145143#: ../Doc/c-api/call.rst:74
146144#, fuzzy
147145msgid ""
148- "Classes can implement the vectorcall protocol by enabling "
149- "the :c:macro: `Py_TPFLAGS_HAVE_VECTORCALL` flag and "
150- "setting :c:member:`~PyTypeObject. tp_vectorcall_offset` to the offset inside "
151- "the object structure where a *vectorcallfunc* appears. This is a pointer to "
152- "a function with the following signature:"
146+ "Classes can implement the vectorcall protocol by enablingthe :c:macro: "
147+ "`Py_TPFLAGS_HAVE_VECTORCALL` flag andsetting :c:member:`~PyTypeObject. "
148+ "tp_vectorcall_offset` to the offset inside the object structure where a "
149+ "*vectorcallfunc* appears. This is a pointer to a function with the following "
150+ "signature:"
153151msgstr ""
154152"Las clases pueden implementar el protocolo vectorcall habilitando el "
155- "indicador :const:`Py_TPFLAGS_HAVE_VECTORCALL` y la "
156- "configuración :c:member: `~PyTypeObject.tp_vectorcall_offset` al "
157- "desplazamiento dentro de la estructura del objeto donde aparece un "
158- "*vectorcallfunc*. Este es un puntero a una función con la siguiente firma:"
153+ "indicador :const:`Py_TPFLAGS_HAVE_VECTORCALL` y laconfiguración :c:member: "
154+ "`~PyTypeObject.tp_vectorcall_offset` al desplazamiento dentro de la "
155+ "estructura del objeto donde aparece un *vectorcallfunc*. Este es un puntero "
156+ "a una función con la siguiente firma:"
159157
160158#: ../Doc/c-api/call.rst:82
161159msgid "*callable* is the object being called."
@@ -235,21 +233,20 @@ msgid ""
235233"include a prepended *self* argument) very efficiently."
236234msgstr ""
237235"Siempre que puedan hacerlo de forma económica (sin asignación adicional), se "
238- "anima a las personas que llaman a "
239- "utilizar :const:`PY_VECTORCALL_ARGUMENTS_OFFSET`. Si lo hace, permitirá que "
240- "las personas que llaman, como los métodos enlazados, realicen sus llamadas "
241- "posteriores (que incluyen un argumento *self* antepuesto) de manera muy "
242- "eficiente."
236+ "anima a las personas que llaman a utilizar :const:"
237+ "`PY_VECTORCALL_ARGUMENTS_OFFSET`. Si lo hace, permitirá que las personas que "
238+ "llaman, como los métodos enlazados, realicen sus llamadas posteriores (que "
239+ "incluyen un argumento *self* antepuesto) de manera muy eficiente."
243240
244241#: ../Doc/c-api/call.rst:113
245242msgid ""
246243"To call an object that implements vectorcall, use a :ref:`call API <capi-"
247244"call>` function as with any other callable. :c:func:`PyObject_Vectorcall` "
248245"will usually be most efficient."
249246msgstr ""
250- "Para llamar a un objeto que implementa vectorcall, use una "
251- "función :ref: `call API <capi-call>` como con cualquier otro "
252- "invocable. :c:func: `PyObject_Vectorcall` normalmente será más eficiente."
247+ "Para llamar a un objeto que implementa vectorcall, use unafunción :ref: "
248+ "`call API <capi-call>` como con cualquier otroinvocable. :c:func: "
249+ "`PyObject_Vectorcall` normalmente será más eficiente."
253250
254251#: ../Doc/c-api/call.rst:119
255252msgid "Recursion Control"
@@ -258,13 +255,12 @@ msgstr "Control de recursión"
258255#: ../Doc/c-api/call.rst:121
259256msgid ""
260257"When using *tp_call*, callees do not need to worry about :ref:`recursion "
261- "<recursion>`: CPython uses :c:func:`Py_EnterRecursiveCall` "
262- "and :c:func: `Py_LeaveRecursiveCall` for calls made using *tp_call*."
258+ "<recursion>`: CPython uses :c:func:`Py_EnterRecursiveCall`and :c:func: "
259+ "`Py_LeaveRecursiveCall` for calls made using *tp_call*."
263260msgstr ""
264- "Cuando se usa *tp_call*, los destinatarios no necesitan preocuparse "
265- "por :ref:`recursividad <recursion>`: CPython "
266- "usa :c:func:`Py_EnterRecursiveCall` y :c:func:`Py_LeaveRecursiveCall` para "
267- "llamadas realizadas usando *tp_call*."
261+ "Cuando se usa *tp_call*, los destinatarios no necesitan preocuparse por :ref:"
262+ "`recursividad <recursion>`: CPython usa :c:func:`Py_EnterRecursiveCall` y :c:"
263+ "func:`Py_LeaveRecursiveCall` para llamadas realizadas usando *tp_call*."
268264
269265#: ../Doc/c-api/call.rst:126
270266msgid ""
@@ -331,13 +327,13 @@ msgstr ""
331327#: ../Doc/c-api/call.rst:164
332328#, fuzzy
333329msgid ""
334- "This is a specialized function, intended to be put in "
335- "the :c:member: `~PyTypeObject.tp_call` slot or be used in an implementation "
336- "of ``tp_call``. It does not check the :c:macro:`Py_TPFLAGS_HAVE_VECTORCALL` "
337- "flag and it does not fall back to ``tp_call``."
330+ "This is a specialized function, intended to be put inthe :c:member: "
331+ "`~PyTypeObject.tp_call` slot or be used in an implementation of ``tp_call``. "
332+ "It does not check the :c:macro:`Py_TPFLAGS_HAVE_VECTORCALL` flag and it does "
333+ "not fall back to ``tp_call``."
338334msgstr ""
339- "Esta es una función especializada, destinada a colocarse en el "
340- "slot :c: member:`~PyTypeObject.tp_call` o usarse en una implementación de "
335+ "Esta es una función especializada, destinada a colocarse en elslot :c: "
336+ "member:`~PyTypeObject.tp_call` o usarse en una implementación de "
341337"``tp_call``. No comprueba el flag :const:`Py_TPFLAGS_HAVE_VECTORCALL` y no "
342338"vuelve a ``tp_call``."
343339
@@ -573,11 +569,11 @@ msgstr ""
573569#: ../Doc/c-api/call.rst:276
574570#, fuzzy
575571msgid ""
576- "Note that if you only pass :c:expr:`PyObject *` "
577- "args, :c:func: `PyObject_CallFunctionObjArgs` is a faster alternative."
572+ "Note that if you only pass :c:expr:`PyObject *`args, :c:func: "
573+ "`PyObject_CallFunctionObjArgs` is a faster alternative."
578574msgstr ""
579- "Tenga en cuenta que si solo pasa :c:type:`PyObject *` "
580- "args, :c:func: `PyObject_CallFunctionObjArgs` es una alternativa más rápida."
575+ "Tenga en cuenta que si solo pasa :c:type:`PyObject *`args, :c:func: "
576+ "`PyObject_CallFunctionObjArgs` es una alternativa más rápida."
581577
582578#: ../Doc/c-api/call.rst:279
583579msgid "The type of *format* was changed from ``char *``."
@@ -609,11 +605,11 @@ msgstr ""
609605#: ../Doc/c-api/call.rst:297
610606#, fuzzy
611607msgid ""
612- "Note that if you only pass :c:expr:`PyObject *` "
613- "args, :c:func: `PyObject_CallMethodObjArgs` is a faster alternative."
608+ "Note that if you only pass :c:expr:`PyObject *`args, :c:func: "
609+ "`PyObject_CallMethodObjArgs` is a faster alternative."
614610msgstr ""
615- "Tenga en cuenta que si solo pasa :c:type:`PyObject *` "
616- "args, :c:func: `PyObject_CallMethodObjArgs` es una alternativa más rápida."
611+ "Tenga en cuenta que si solo pasa :c:type:`PyObject *`args, :c:func: "
612+ "`PyObject_CallMethodObjArgs` es una alternativa más rápida."
617613
618614#: ../Doc/c-api/call.rst:300
619615msgid "The types of *name* and *format* were changed from ``char *``."
@@ -622,9 +618,9 @@ msgstr "Los tipos de *name* y *format* se cambiaron desde ``char *``."
622618#: ../Doc/c-api/call.rst:306
623619#, fuzzy
624620msgid ""
625- "Call a callable Python object *callable*, with a variable number "
626- "of :c:expr: `PyObject *` arguments. The arguments are provided as a variable "
627- "number of parameters followed by *NULL*."
621+ "Call a callable Python object *callable*, with a variable numberof :c:expr: "
622+ "`PyObject *` arguments. The arguments are provided as a variable number of "
623+ "parameters followed by *NULL*."
628624msgstr ""
629625"Llame a un objeto de Python invocable *callable*, con un número variable de "
630626"argumentos :c:type:`PyObject *`. Los argumentos se proporcionan como un "
@@ -672,9 +668,9 @@ msgstr ""
672668
673669#: ../Doc/c-api/call.rst:353
674670msgid ""
675- "Call a callable Python object *callable*. The arguments are the same as "
676- "for : c:type:`vectorcallfunc`. If *callable* supports vectorcall_, this "
677- "directly calls the vectorcall function stored in *callable*."
671+ "Call a callable Python object *callable*. The arguments are the same asfor : "
672+ "c:type:`vectorcallfunc`. If *callable* supports vectorcall_, this directly "
673+ "calls the vectorcall function stored in *callable*."
678674msgstr ""
679675"Llama a un objeto de Python invocable *callable*. Los argumentos son los "
680676"mismos que para :c:type:`vectorcallfunc`. Si *callable* admite vectorcall_, "
@@ -711,10 +707,10 @@ msgid ""
711707"method is given as a Python string *name*. The object whose method is called "
712708"is *args[0]*, and the *args* array starting at *args[1]* represents the "
713709"arguments of the call. There must be at least one positional argument. "
714- "*nargsf* is the number of positional arguments including *args[0]*, "
715- "plus :c: macro:`PY_VECTORCALL_ARGUMENTS_OFFSET` if the value of ``args[0]`` "
716- "may temporarily be changed. Keyword arguments can be passed just like "
717- "in :c:func: `PyObject_Vectorcall`."
710+ "*nargsf* is the number of positional arguments including *args[0]*,plus :c: "
711+ "macro:`PY_VECTORCALL_ARGUMENTS_OFFSET` if the value of ``args[0]`` may "
712+ "temporarily be changed. Keyword arguments can be passed just likein :c:func: "
713+ "`PyObject_Vectorcall`."
718714msgstr ""
719715"Llama a un método usando la convención de llamada vectorcall. El nombre del "
720716"método se proporciona como una cadena de Python *name*. El objeto cuyo "