@@ -10,7 +10,8 @@ msgstr ""
10
10
"POT-Creation-Date :2020-02-09 18:46+0900\n "
11
11
"PO-Revision-Date :2018-06-20 04:47+0000\n "
12
12
"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 "
14
15
"Language :pt_BR\n "
15
16
"MIME-Version :1.0\n "
16
17
"Content-Type :text/plain; charset=UTF-8\n "
@@ -53,21 +54,21 @@ msgid ""
53
54
"It is important to understand that the management of the Python heap is "
54
55
"performed by the interpreter itself and that the user has no control over "
55
56
"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."
59
60
msgstr ""
60
61
61
62
#: ../../c-api/memory.rst:49
62
63
msgid ""
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::"
71
72
msgstr ""
72
73
73
74
#: ../../c-api/memory.rst:68
@@ -84,8 +85,8 @@ msgid ""
84
85
"memory manager. For example, this is required when the interpreter is "
85
86
"extended with new object types written in C. Another reason for using the "
86
87
"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 "
89
90
"requests to the Python memory manager causes the interpreter to have a more "
90
91
"accurate image of its memory footprint as a whole. Consequently, under "
91
92
"certain circumstances, the Python memory manager may or may not trigger "
@@ -102,25 +103,25 @@ msgstr "Interface da Memória"
102
103
#: ../../c-api/memory.rst:92
103
104
msgid ""
104
105
"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:"
107
108
msgstr ""
108
109
109
110
#: ../../c-api/memory.rst:99
110
111
msgid ""
111
112
"Allocates *n* bytes and returns a pointer of type :c:type:`void\\ *` to the "
112
113
"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 "
115
116
"way."
116
117
msgstr ""
117
118
118
119
#: ../../c-api/memory.rst:107
119
120
msgid ""
120
121
"Resizes the memory block pointed to by *p* to *n* bytes. The contents will "
121
122
"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 "
124
125
"non-*NULL*. Unless *p* is *NULL*, it must have been returned by a previous "
125
126
"call to :c:func:`PyMem_Malloc` or :c:func:`PyMem_Realloc`. If the request "
126
127
"fails, :c:func:`PyMem_Realloc` returns *NULL* and *p* remains a valid "
@@ -129,16 +130,16 @@ msgstr ""
129
130
130
131
#: ../../c-api/memory.rst:119
131
132
msgid ""
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`. "
134
135
"Otherwise, or if ``PyMem_Free(p)`` has been called before, undefined "
135
136
"behavior occurs. If *p* is *NULL*, no operation is performed."
136
137
msgstr ""
137
138
138
139
#: ../../c-api/memory.rst:124
139
140
msgid ""
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."
142
143
msgstr ""
143
144
144
145
#: ../../c-api/memory.rst:130
@@ -152,8 +153,8 @@ msgstr ""
152
153
msgid ""
153
154
"Same as :c:func:`PyMem_Realloc`, but the memory block is resized to ``(n * "
154
155
"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 "
157
158
"the original value of p to avoid losing memory when handling errors."
158
159
msgstr ""
159
160
@@ -179,13 +180,13 @@ msgstr ""
179
180
180
181
#: ../../c-api/memory.rst:159
181
182
msgid "Object allocators"
182
- msgstr ""
183
+ msgstr "Alocadores de objeto "
183
184
184
185
#: ../../c-api/memory.rst:161
185
186
msgid ""
186
187
"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."
189
190
msgstr ""
190
191
191
192
#: ../../c-api/memory.rst:165
@@ -227,9 +228,9 @@ msgstr ""
227
228
228
229
#: ../../c-api/memory.rst:191
229
230
msgid ""
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`."
233
234
msgstr ""
234
235
235
236
#: ../../c-api/memory.rst:194
@@ -240,9 +241,9 @@ msgstr ""
240
241
241
242
#: ../../c-api/memory.rst:200
242
243
msgid ""
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 "
246
247
"called before, undefined behavior occurs."
247
248
msgstr ""
248
249
@@ -306,8 +307,8 @@ msgstr ":c:func:`malloc` e :c:func:`free` do contrário."
306
307
307
308
#: ../../c-api/memory.rst:235
308
309
msgid ""
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."
311
312
msgstr ""
312
313
313
314
#: ../../c-api/memory.rst:243
@@ -317,8 +318,8 @@ msgstr "Exemplos"
317
318
#: ../../c-api/memory.rst:245
318
319
msgid ""
319
320
"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::"
322
323
msgstr ""
323
324
324
325
#: ../../c-api/memory.rst:258
@@ -331,20 +332,19 @@ msgid ""
331
332
"functions belonging to the same set. Indeed, it is required to use the same "
332
333
"memory API family for a given memory block, so that the risk of mixing "
333
334
"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. ::"
336
337
msgstr ""
337
338
338
339
#: ../../c-api/memory.rst:285
339
340
msgid ""
340
341
"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`."
344
344
msgstr ""
345
345
346
346
#: ../../c-api/memory.rst:289
347
347
msgid ""
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."
350
350
msgstr ""