@@ -10,7 +10,8 @@ msgstr ""
1010"POT-Creation-Date :2020-02-09 18:46+0900\n "
1111"PO-Revision-Date :2018-06-20 04:47+0000\n "
1212"Last-Translator :tomo\n "
13- "Language-Team :Portuguese (Brazil) (http://www.transifex.com/python-doc/python-27/language/pt_BR/)\n "
13+ "Language-Team :Portuguese (Brazil) (http://www.transifex.com/python-doc/ "
14+ "python-27/language/pt_BR/)\n "
1415"Language :pt_BR\n "
1516"MIME-Version :1.0\n "
1617"Content-Type :text/plain; charset=UTF-8\n "
@@ -53,21 +54,21 @@ msgid ""
5354"It is important to understand that the management of the Python heap is "
5455"performed by the interpreter itself and that the user has no control over "
5556"it, even if they regularly manipulate object pointers to memory blocks "
56- "inside that heap. The allocation of heap space for Python objects and other"
57- " internal buffers is performed on demand by the Python memory manager "
58- "through the Python/C API functions listed in this document."
57+ "inside that heap. The allocation of heap space for Python objects and other "
58+ "internal buffers is performed on demand by the Python memory manager through "
59+ "the Python/C API functions listed in this document."
5960msgstr ""
6061
6162#: ../../c-api/memory.rst:49
6263msgid ""
63- "To avoid memory corruption, extension writers should never try to operate on"
64- " Python objects with the functions exported by the C library: "
65- ":c:func: `malloc`, :c:func:`calloc`, :c:func:`realloc` and :c:func:`free`. "
66- "This will result in mixed calls between the C allocator and the Python "
67- "memory manager with fatal consequences, because they implement different "
68- "algorithms and operate on different heaps. However, one may safely allocate"
69- " and release memory blocks with the C library allocator for individual "
70- "purposes, as shown in the following example::"
64+ "To avoid memory corruption, extension writers should never try to operate on "
65+ "Python objects with the functions exported by the C library::c:func: "
66+ "`malloc`, :c:func:`calloc`, :c:func:`realloc` and :c:func:`free`. This will "
67+ "result in mixed calls between the C allocator and the Python memory manager "
68+ "with fatal consequences, because they implement different algorithms and "
69+ "operate on different heaps. However, one may safely allocate and release "
70+ "memory blocks with the C library allocator for individual purposes, as shown "
71+ "in the following example::"
7172msgstr ""
7273
7374#: ../../c-api/memory.rst:68
@@ -84,8 +85,8 @@ msgid ""
8485"memory manager. For example, this is required when the interpreter is "
8586"extended with new object types written in C. Another reason for using the "
8687"Python heap is the desire to *inform* the Python memory manager about the "
87- "memory needs of the extension module. Even when the requested memory is used"
88- " exclusively for internal, highly-specific purposes, delegating all memory "
88+ "memory needs of the extension module. Even when the requested memory is used "
89+ "exclusively for internal, highly-specific purposes, delegating all memory "
8990"requests to the Python memory manager causes the interpreter to have a more "
9091"accurate image of its memory footprint as a whole. Consequently, under "
9192"certain circumstances, the Python memory manager may or may not trigger "
@@ -102,25 +103,25 @@ msgstr "Interface da Memória"
102103#: ../../c-api/memory.rst:92
103104msgid ""
104105"The following function sets, modeled after the ANSI C standard, but "
105- "specifying behavior when requesting zero bytes, are available for allocating"
106- " and releasing memory from the Python heap:"
106+ "specifying behavior when requesting zero bytes, are available for allocating "
107+ "and releasing memory from the Python heap:"
107108msgstr ""
108109
109110#: ../../c-api/memory.rst:99
110111msgid ""
111112"Allocates *n* bytes and returns a pointer of type :c:type:`void\\ *` to the "
112113"allocated memory, or *NULL* if the request fails. Requesting zero bytes "
113- "returns a distinct non-*NULL* pointer if possible, as if ``PyMem_Malloc(1)``"
114- " had been called instead. The memory will not have been initialized in any "
114+ "returns a distinct non-*NULL* pointer if possible, as if ``PyMem_Malloc(1)`` "
115+ "had been called instead. The memory will not have been initialized in any "
115116"way."
116117msgstr ""
117118
118119#: ../../c-api/memory.rst:107
119120msgid ""
120121"Resizes the memory block pointed to by *p* to *n* bytes. The contents will "
121122"be unchanged to the minimum of the old and the new sizes. If *p* is *NULL*, "
122- "the call is equivalent to ``PyMem_Malloc(n)``; else if *n* is equal to zero,"
123- " the memory block is resized but is not freed, and the returned pointer is "
123+ "the call is equivalent to ``PyMem_Malloc(n)``; else if *n* is equal to zero, "
124+ "the memory block is resized but is not freed, and the returned pointer is "
124125"non-*NULL*. Unless *p* is *NULL*, it must have been returned by a previous "
125126"call to :c:func:`PyMem_Malloc` or :c:func:`PyMem_Realloc`. If the request "
126127"fails, :c:func:`PyMem_Realloc` returns *NULL* and *p* remains a valid "
@@ -129,16 +130,16 @@ msgstr ""
129130
130131#: ../../c-api/memory.rst:119
131132msgid ""
132- "Frees the memory block pointed to by *p*, which must have been returned by a"
133- " previous call to :c:func:`PyMem_Malloc` or :c:func:`PyMem_Realloc`. "
133+ "Frees the memory block pointed to by *p*, which must have been returned by a "
134+ "previous call to :c:func:`PyMem_Malloc` or :c:func:`PyMem_Realloc`. "
134135"Otherwise, or if ``PyMem_Free(p)`` has been called before, undefined "
135136"behavior occurs. If *p* is *NULL*, no operation is performed."
136137msgstr ""
137138
138139#: ../../c-api/memory.rst:124
139140msgid ""
140- "The following type-oriented macros are provided for convenience. Note that"
141- " *TYPE* refers to any C type."
141+ "The following type-oriented macros are provided for convenience. Note that "
142+ "*TYPE* refers to any C type."
142143msgstr ""
143144
144145#: ../../c-api/memory.rst:130
@@ -152,8 +153,8 @@ msgstr ""
152153msgid ""
153154"Same as :c:func:`PyMem_Realloc`, but the memory block is resized to ``(n * "
154155"sizeof(TYPE))`` bytes. Returns a pointer cast to :c:type:`TYPE\\ *`. On "
155- "return, *p* will be a pointer to the new memory area, or *NULL* in the event"
156- " of failure. This is a C preprocessor macro; p is always reassigned. Save "
156+ "return, *p* will be a pointer to the new memory area, or *NULL* in the event "
157+ "of failure. This is a C preprocessor macro; p is always reassigned. Save "
157158"the original value of p to avoid losing memory when handling errors."
158159msgstr ""
159160
@@ -179,13 +180,13 @@ msgstr ""
179180
180181#: ../../c-api/memory.rst:159
181182msgid "Object allocators"
182- msgstr ""
183+ msgstr "Alocadores de objeto "
183184
184185#: ../../c-api/memory.rst:161
185186msgid ""
186187"The following function sets, modeled after the ANSI C standard, but "
187- "specifying behavior when requesting zero bytes, are available for allocating"
188- " and releasing memory from the Python heap."
188+ "specifying behavior when requesting zero bytes, are available for allocating "
189+ "and releasing memory from the Python heap."
189190msgstr ""
190191
191192#: ../../c-api/memory.rst:165
@@ -227,9 +228,9 @@ msgstr ""
227228
228229#: ../../c-api/memory.rst:191
229230msgid ""
230- "Unless *p* is *NULL*, it must have been returned by a previous call to "
231- ":c: func:`PyObject_Malloc`, :c:func:`PyObject_Realloc` or "
232- ":c:func: `PyObject_Calloc`."
231+ "Unless *p* is *NULL*, it must have been returned by a previous call to:c: "
232+ "func:`PyObject_Malloc`, :c:func:`PyObject_Realloc` or:c:func: "
233+ "`PyObject_Calloc`."
233234msgstr ""
234235
235236#: ../../c-api/memory.rst:194
@@ -240,9 +241,9 @@ msgstr ""
240241
241242#: ../../c-api/memory.rst:200
242243msgid ""
243- "Frees the memory block pointed to by *p*, which must have been returned by a"
244- " previous call to :c:func:`PyObject_Malloc`, :c:func:`PyObject_Realloc` or "
245- ":c: func:`PyObject_Calloc`. Otherwise, or if ``PyObject_Free(p)`` has been "
244+ "Frees the memory block pointed to by *p*, which must have been returned by a "
245+ "previous call to :c:func:`PyObject_Malloc`, :c:func:`PyObject_Realloc` or:c: "
246+ "func:`PyObject_Calloc`. Otherwise, or if ``PyObject_Free(p)`` has been "
246247"called before, undefined behavior occurs."
247248msgstr ""
248249
@@ -306,8 +307,8 @@ msgstr ":c:func:`malloc` e :c:func:`free` do contrário."
306307
307308#: ../../c-api/memory.rst:235
308309msgid ""
309- "The threshold changed from 256 to 512 bytes. The arena allocator now uses "
310- ":c: func:`mmap` if available."
310+ "The threshold changed from 256 to 512 bytes. The arena allocator now uses:c: "
311+ "func:`mmap` if available."
311312msgstr ""
312313
313314#: ../../c-api/memory.rst:243
@@ -317,8 +318,8 @@ msgstr "Exemplos"
317318#: ../../c-api/memory.rst:245
318319msgid ""
319320"Here is the example from section :ref:`memoryoverview`, rewritten so that "
320- "the I/O buffer is allocated from the Python heap by using the first function"
321- " set::"
321+ "the I/O buffer is allocated from the Python heap by using the first function "
322+ "set::"
322323msgstr ""
323324
324325#: ../../c-api/memory.rst:258
@@ -331,20 +332,19 @@ msgid ""
331332"functions belonging to the same set. Indeed, it is required to use the same "
332333"memory API family for a given memory block, so that the risk of mixing "
333334"different allocators is reduced to a minimum. The following code sequence "
334- "contains two errors, one of which is labeled as *fatal* because it mixes two"
335- " different allocators operating on different heaps. ::"
335+ "contains two errors, one of which is labeled as *fatal* because it mixes two "
336+ "different allocators operating on different heaps. ::"
336337msgstr ""
337338
338339#: ../../c-api/memory.rst:285
339340msgid ""
340341"In addition to the functions aimed at handling raw memory blocks from the "
341- "Python heap, objects in Python are allocated and released with "
342- ":c:func:`PyObject_New`, :c:func:`PyObject_NewVar` and "
343- ":c:func:`PyObject_Del`."
342+ "Python heap, objects in Python are allocated and released with :c:func:"
343+ "`PyObject_New`, :c:func:`PyObject_NewVar` and :c:func:`PyObject_Del`."
344344msgstr ""
345345
346346#: ../../c-api/memory.rst:289
347347msgid ""
348- "These will be explained in the next chapter on defining and implementing new"
349- " object types in C."
348+ "These will be explained in the next chapter on defining and implementing new "
349+ "object types in C."
350350msgstr ""