@@ -18,7 +18,8 @@ msgstr ""
1818"POT-Creation-Date : 2020-02-09 12:40+0000\n "
1919"PO-Revision-Date : 2017-02-16 17:39+0000\n "
2020"Last-Translator : Marco Rougeth <marco@rougeth.com>, 2020\n "
21- "Language-Team : Portuguese (Brazil) (https://www.transifex.com/python-doc/teams/5390/pt_BR/)\n "
21+ "Language-Team : Portuguese (Brazil) (https://www.transifex.com/python-doc/ "
22+ "teams/5390/pt_BR/)\n "
2223"Language : pt_BR\n "
2324"MIME-Version : 1.0\n "
2425"Content-Type : text/plain; charset=UTF-8\n "
@@ -47,13 +48,13 @@ msgstr ""
4748
4849#: ../../c-api/structures.rst:21
4950msgid ""
50- "All object types are extensions of this type. This is a type which contains"
51- " the information Python needs to treat a pointer to an object as an object."
52- " In a normal \" release\" build, it contains only the object's reference "
53- "count and a pointer to the corresponding type object. Nothing is actually "
54- "declared to be a :c:type:`PyObject`, but every pointer to a Python object "
55- "can be cast to a :c:type:`PyObject*`. Access to the members must be done by"
56- " using the macros :c:macro:`Py_REFCNT` and :c:macro:`Py_TYPE`."
51+ "All object types are extensions of this type. This is a type which contains "
52+ "the information Python needs to treat a pointer to an object as an object. "
53+ "In a normal \" release\" build, it contains only the object's reference count "
54+ "and a pointer to the corresponding type object. Nothing is actually declared "
55+ "to be a :c:type:`PyObject`, but every pointer to a Python object can be cast "
56+ "to a :c:type:`PyObject*`. Access to the members must be done by using the "
57+ "macros :c:macro:`Py_REFCNT` and :c:macro:`Py_TYPE`."
5758msgstr ""
5859
5960#: ../../c-api/structures.rst:33
@@ -77,8 +78,8 @@ msgstr ""
7778
7879#: ../../c-api/structures.rst:52
7980msgid ""
80- "This is a macro used when declaring new types which represent objects with a"
81- " length that varies from instance to instance. The PyObject_VAR_HEAD macro "
81+ "This is a macro used when declaring new types which represent objects with a "
82+ "length that varies from instance to instance. The PyObject_VAR_HEAD macro "
8283"expands to::"
8384msgstr ""
8485
@@ -106,15 +107,15 @@ msgstr ""
106107
107108#: ../../c-api/structures.rst:88
108109msgid ""
109- "This is a macro which expands to initialization values for a new "
110- ":c:type: `PyObject` type. This macro expands to::"
110+ "This is a macro which expands to initialization values for a new :c:type: "
111+ "`PyObject` type. This macro expands to::"
111112msgstr ""
112113
113114#: ../../c-api/structures.rst:97
114115msgid ""
115- "This is a macro which expands to initialization values for a new "
116- ":c:type: `PyVarObject` type, including the :attr:`ob_size` field. This macro "
117- "expands to::"
116+ "This is a macro which expands to initialization values for a new :c:type: "
117+ "`PyVarObject` type, including the :attr:`ob_size` field. This macro expands "
118+ "to::"
118119msgstr ""
119120
120121#: ../../c-api/structures.rst:107
@@ -129,20 +130,20 @@ msgstr ""
129130
130131#: ../../c-api/structures.rst:117
131132msgid ""
132- "Type of the functions used to implement Python callables in C with signature "
133- " :const:`METH_VARARGS | METH_KEYWORDS`."
133+ "Type of the functions used to implement Python callables in C with "
134+ "signature :const:`METH_VARARGS | METH_KEYWORDS`."
134135msgstr ""
135136
136137#: ../../c-api/structures.rst:123
137138msgid ""
138- "Type of the functions used to implement Python callables in C with signature "
139- " :const:`METH_FASTCALL`."
139+ "Type of the functions used to implement Python callables in C with "
140+ "signature :const:`METH_FASTCALL`."
140141msgstr ""
141142
142143#: ../../c-api/structures.rst:129
143144msgid ""
144- "Type of the functions used to implement Python callables in C with signature "
145- " :const:`METH_FASTCALL | METH_KEYWORDS`."
145+ "Type of the functions used to implement Python callables in C with "
146+ "signature :const:`METH_FASTCALL | METH_KEYWORDS`."
146147msgstr ""
147148
148149#: ../../c-api/structures.rst:135
@@ -233,20 +234,19 @@ msgstr ""
233234
234235#: ../../c-api/structures.rst:164
235236msgid ""
236- "There are four basic calling conventions for positional arguments and two of"
237- " them can be combined with :const:`METH_KEYWORDS` to support also keyword "
237+ "There are four basic calling conventions for positional arguments and two of "
238+ "them can be combined with :const:`METH_KEYWORDS` to support also keyword "
238239"arguments. So there are a total of 6 calling conventions:"
239240msgstr ""
240241
241242#: ../../c-api/structures.rst:170
242243msgid ""
243- "This is the typical calling convention, where the methods have the type "
244- ":c:type:`PyCFunction`. The function expects two :c:type:`PyObject\\ *` "
245- "values. The first one is the *self* object for methods; for module "
246- "functions, it is the module object. The second parameter (often called "
247- "*args*) is a tuple object representing all arguments. This parameter is "
248- "typically processed using :c:func:`PyArg_ParseTuple` or "
249- ":c:func:`PyArg_UnpackTuple`."
244+ "This is the typical calling convention, where the methods have the type :c:"
245+ "type:`PyCFunction`. The function expects two :c:type:`PyObject\\ *` values. "
246+ "The first one is the *self* object for methods; for module functions, it is "
247+ "the module object. The second parameter (often called *args*) is a tuple "
248+ "object representing all arguments. This parameter is typically processed "
249+ "using :c:func:`PyArg_ParseTuple` or :c:func:`PyArg_UnpackTuple`."
250250msgstr ""
251251
252252#: ../../c-api/structures.rst:180
@@ -261,10 +261,10 @@ msgstr ""
261261#: ../../c-api/structures.rst:189
262262msgid ""
263263"Fast calling convention supporting only positional arguments. The methods "
264- "have the type :c:type:`_PyCFunctionFast`. The first parameter is *self*, the"
265- " second parameter is a C array of :c:type:`PyObject\\ *` values indicating "
266- "the arguments and the third parameter is the number of arguments (the length"
267- " of the array)."
264+ "have the type :c:type:`_PyCFunctionFast`. The first parameter is *self*, the "
265+ "second parameter is a C array of :c:type:`PyObject\\ *` values indicating the "
266+ "arguments and the third parameter is the number of arguments (the length of "
267+ "the array)."
268268msgstr ""
269269
270270#: ../../c-api/structures.rst:195 ../../c-api/structures.rst:210
@@ -293,8 +293,8 @@ msgstr ""
293293
294294#: ../../c-api/structures.rst:226
295295msgid ""
296- "Methods with a single object argument can be listed with the :const:`METH_O`"
297- " flag, instead of invoking :c:func:`PyArg_ParseTuple` with a ``\" O\" `` "
296+ "Methods with a single object argument can be listed with the :const:`METH_O` "
297+ "flag, instead of invoking :c:func:`PyArg_ParseTuple` with a ``\" O\" `` "
298298"argument. They have the type :c:type:`PyCFunction`, with the *self* "
299299"parameter, and a :c:type:`PyObject\\ *` parameter representing the single "
300300"argument."
@@ -310,9 +310,9 @@ msgstr ""
310310
311311#: ../../c-api/structures.rst:242
312312msgid ""
313- "The method will be passed the type object as the first parameter rather than"
314- " an instance of the type. This is used to create *class methods*, similar "
315- "to what is created when using the :func:`classmethod` built-in function."
313+ "The method will be passed the type object as the first parameter rather than "
314+ "an instance of the type. This is used to create *class methods*, similar to "
315+ "what is created when using the :func:`classmethod` built-in function."
316316msgstr ""
317317
318318#: ../../c-api/structures.rst:252
@@ -333,12 +333,12 @@ msgid ""
333333"The method will be loaded in place of existing definitions. Without "
334334"*METH_COEXIST*, the default is to skip repeated definitions. Since slot "
335335"wrappers are loaded before the method table, the existence of a "
336- "*sq_contains* slot, for example, would generate a wrapped method named "
337- ":meth: `__contains__` and preclude the loading of a corresponding PyCFunction"
338- " with the same name. With the flag defined, the PyCFunction will be loaded "
339- "in place of the wrapper object and will co-exist with the slot. This is "
340- "helpful because calls to PyCFunctions are optimized more than wrapper object"
341- " calls."
336+ "*sq_contains* slot, for example, would generate a wrapped method named :meth: "
337+ "`__contains__` and preclude the loading of a corresponding PyCFunction with "
338+ "the same name. With the flag defined, the PyCFunction will be loaded in "
339+ "place of the wrapper object and will co-exist with the slot. This is "
340+ "helpful because calls to PyCFunctions are optimized more than wrapper object "
341+ "calls."
342342msgstr ""
343343
344344#: ../../c-api/structures.rst:275
@@ -510,7 +510,7 @@ msgstr ""
510510
511511#: ../../c-api/structures.rst:320
512512msgid "long long"
513- msgstr ""
513+ msgstr "long long "
514514
515515#: ../../c-api/structures.rst:321
516516msgid "T_ULONGLONG"
@@ -526,27 +526,27 @@ msgstr ""
526526
527527#: ../../c-api/structures.rst:325
528528msgid ""
529- ":c:macro:`T_OBJECT` and :c:macro:`T_OBJECT_EX` differ in that "
530- ":c:macro: `T_OBJECT` returns ``None`` if the member is ``NULL`` and "
531- ":c:macro: `T_OBJECT_EX` raises an :exc:`AttributeError`. Try to use "
532- ":c:macro: `T_OBJECT_EX` over :c:macro:`T_OBJECT` because "
533- ":c:macro:`T_OBJECT_EX` handles use of the :keyword:`del` statement on that "
534- "attribute more correctly than :c:macro:`T_OBJECT`."
529+ ":c:macro:`T_OBJECT` and :c:macro:`T_OBJECT_EX` differ in that :c:macro: "
530+ "`T_OBJECT` returns ``None`` if the member is ``NULL`` and :c:macro: "
531+ "`T_OBJECT_EX` raises an :exc:`AttributeError`. Try to use :c:macro: "
532+ "`T_OBJECT_EX` over :c:macro:`T_OBJECT` because :c:macro:`T_OBJECT_EX` "
533+ "handles use of the :keyword:`del` statement on that attribute more correctly "
534+ "than :c:macro:`T_OBJECT`."
535535msgstr ""
536536
537537#: ../../c-api/structures.rst:332
538538msgid ""
539539":attr:`flags` can be ``0`` for write and read access or :c:macro:`READONLY` "
540- "for read-only access. Using :c:macro:`T_STRING` for :attr:`type` implies "
541- ":c: macro:`READONLY`. :c:macro:`T_STRING` data is interpreted as UTF-8. Only"
542- " :c: macro:`T_OBJECT` and :c:macro:`T_OBJECT_EX` members can be deleted. "
543- "(They are set to ``NULL``)."
540+ "for read-only access. Using :c:macro:`T_STRING` for :attr:`type` implies :c: "
541+ "macro:`READONLY`. :c:macro:`T_STRING` data is interpreted as UTF-8. Only :c: "
542+ "macro:`T_OBJECT` and :c:macro:`T_OBJECT_EX` members can be deleted. (They "
543+ "are set to ``NULL``)."
544544msgstr ""
545545
546546#: ../../c-api/structures.rst:341
547547msgid ""
548- "Structure to define property-like access for a type. See also description of"
549- " the :c:member:`PyTypeObject.tp_getset` slot."
548+ "Structure to define property-like access for a type. See also description of "
549+ "the :c:member:`PyTypeObject.tp_getset` slot."
550550msgstr ""
551551
552552#: ../../c-api/structures.rst:347
@@ -579,8 +579,8 @@ msgstr ""
579579
580580#: ../../c-api/structures.rst:351
581581msgid ""
582- "optional C function to set or delete the attribute, if omitted the attribute"
583- " is readonly"
582+ "optional C function to set or delete the attribute, if omitted the attribute "
583+ "is readonly"
584584msgstr ""
585585
586586#: ../../c-api/structures.rst:355
@@ -612,8 +612,8 @@ msgstr ""
612612
613613#: ../../c-api/structures.rst:367
614614msgid ""
615- "It should return a new reference on success or ``NULL`` with a set exception"
616- " on failure."
615+ "It should return a new reference on success or ``NULL`` with a set exception "
616+ "on failure."
617617msgstr ""
618618
619619#: ../../c-api/structures.rst:370
0 commit comments