-
-
Notifications
You must be signed in to change notification settings - Fork 404
Expand file tree
/
Copy pathmemory.po
More file actions
809 lines (664 loc) · 24.1 KB
/
memory.po
File metadata and controls
809 lines (664 loc) · 24.1 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
# Copyright (C) 2001-2020, Python Software Foundation
# This file is distributed under the same license as the Python package.
# Maintained by the python-doc-es workteam.
# docs-es@python.org / https://mail.python.org/mailman3/lists/docs-es.python.org/
# Check https://github.com/PyCampES/python-docs-es/blob/3.7/TRANSLATORS to get the list of volunteers
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.7\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2019-05-06 11:59-0400\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: python-doc-es (https://mail.python.org/mailman3/lists/docs-es.python.org)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../Doc/c-api/memory.rst:8
msgid "Memory Management"
msgstr ""
#: ../Doc/c-api/memory.rst:17
msgid "Overview"
msgstr ""
#: ../Doc/c-api/memory.rst:19
msgid ""
"Memory management in Python involves a private heap containing all Python "
"objects and data structures. The management of this private heap is ensured "
"internally by the *Python memory manager*. The Python memory manager has "
"different components which deal with various dynamic storage management "
"aspects, like sharing, segmentation, preallocation or caching."
msgstr ""
#: ../Doc/c-api/memory.rst:25
msgid ""
"At the lowest level, a raw memory allocator ensures that there is enough "
"room in the private heap for storing all Python-related data by interacting "
"with the memory manager of the operating system. On top of the raw memory "
"allocator, several object-specific allocators operate on the same heap and "
"implement distinct memory management policies adapted to the peculiarities "
"of every object type. For example, integer objects are managed differently "
"within the heap than strings, tuples or dictionaries because integers imply "
"different storage requirements and speed/space tradeoffs. The Python memory "
"manager thus delegates some of the work to the object-specific allocators, "
"but ensures that the latter operate within the bounds of the private heap."
msgstr ""
#: ../Doc/c-api/memory.rst:36
msgid ""
"It is important to understand that the management of the Python heap is "
"performed by the interpreter itself and that the user has no control over "
"it, even if they regularly manipulate object pointers to memory blocks "
"inside that heap. The allocation of heap space for Python objects and other "
"internal buffers is performed on demand by the Python memory manager through "
"the Python/C API functions listed in this document."
msgstr ""
#: ../Doc/c-api/memory.rst:49
msgid ""
"To avoid memory corruption, extension writers should never try to operate on "
"Python objects with the functions exported by the C library: :c:func:"
"`malloc`, :c:func:`calloc`, :c:func:`realloc` and :c:func:`free`. This will "
"result in mixed calls between the C allocator and the Python memory manager "
"with fatal consequences, because they implement different algorithms and "
"operate on different heaps. However, one may safely allocate and release "
"memory blocks with the C library allocator for individual purposes, as shown "
"in the following example::"
msgstr ""
#: ../Doc/c-api/memory.rst:68
msgid ""
"In this example, the memory request for the I/O buffer is handled by the C "
"library allocator. The Python memory manager is involved only in the "
"allocation of the string object returned as a result."
msgstr ""
#: ../Doc/c-api/memory.rst:72
msgid ""
"In most situations, however, it is recommended to allocate memory from the "
"Python heap specifically because the latter is under control of the Python "
"memory manager. For example, this is required when the interpreter is "
"extended with new object types written in C. Another reason for using the "
"Python heap is the desire to *inform* the Python memory manager about the "
"memory needs of the extension module. Even when the requested memory is used "
"exclusively for internal, highly-specific purposes, delegating all memory "
"requests to the Python memory manager causes the interpreter to have a more "
"accurate image of its memory footprint as a whole. Consequently, under "
"certain circumstances, the Python memory manager may or may not trigger "
"appropriate actions, like garbage collection, memory compaction or other "
"preventive procedures. Note that by using the C library allocator as shown "
"in the previous example, the allocated memory for the I/O buffer escapes "
"completely the Python memory manager."
msgstr ""
#: ../Doc/c-api/memory.rst:88
msgid ""
"The :envvar:`PYTHONMALLOC` environment variable can be used to configure the "
"memory allocators used by Python."
msgstr ""
#: ../Doc/c-api/memory.rst:91
msgid ""
"The :envvar:`PYTHONMALLOCSTATS` environment variable can be used to print "
"statistics of the :ref:`pymalloc memory allocator <pymalloc>` every time a "
"new pymalloc object arena is created, and on shutdown."
msgstr ""
#: ../Doc/c-api/memory.rst:97
msgid "Raw Memory Interface"
msgstr ""
#: ../Doc/c-api/memory.rst:99
msgid ""
"The following function sets are wrappers to the system allocator. These "
"functions are thread-safe, the :term:`GIL <global interpreter lock>` does "
"not need to be held."
msgstr ""
#: ../Doc/c-api/memory.rst:103
msgid ""
"The :ref:`default raw memory allocator <default-memory-allocators>` uses the "
"following functions: :c:func:`malloc`, :c:func:`calloc`, :c:func:`realloc` "
"and :c:func:`free`; call ``malloc(1)`` (or ``calloc(1, 1)``) when requesting "
"zero bytes."
msgstr ""
#: ../Doc/c-api/memory.rst:112 ../Doc/c-api/memory.rst:183
#: ../Doc/c-api/memory.rst:285
msgid ""
"Allocates *n* bytes and returns a pointer of type :c:type:`void\\*` to the "
"allocated memory, or *NULL* if the request fails."
msgstr ""
#: ../Doc/c-api/memory.rst:115
msgid ""
"Requesting zero bytes returns a distinct non-*NULL* pointer if possible, as "
"if ``PyMem_RawMalloc(1)`` had been called instead. The memory will not have "
"been initialized in any way."
msgstr ""
#: ../Doc/c-api/memory.rst:122 ../Doc/c-api/memory.rst:193
#: ../Doc/c-api/memory.rst:295
msgid ""
"Allocates *nelem* elements each whose size in bytes is *elsize* and returns "
"a pointer of type :c:type:`void\\*` to the allocated memory, or *NULL* if "
"the request fails. The memory is initialized to zeros."
msgstr ""
#: ../Doc/c-api/memory.rst:126
msgid ""
"Requesting zero elements or elements of size zero bytes returns a distinct "
"non-*NULL* pointer if possible, as if ``PyMem_RawCalloc(1, 1)`` had been "
"called instead."
msgstr ""
#: ../Doc/c-api/memory.rst:135 ../Doc/c-api/memory.rst:206
#: ../Doc/c-api/memory.rst:308
msgid ""
"Resizes the memory block pointed to by *p* to *n* bytes. The contents will "
"be unchanged to the minimum of the old and the new sizes."
msgstr ""
#: ../Doc/c-api/memory.rst:138
msgid ""
"If *p* is *NULL*, the call is equivalent to ``PyMem_RawMalloc(n)``; else if "
"*n* is equal to zero, the memory block is resized but is not freed, and the "
"returned pointer is non-*NULL*."
msgstr ""
#: ../Doc/c-api/memory.rst:142
msgid ""
"Unless *p* is *NULL*, it must have been returned by a previous call to :c:"
"func:`PyMem_RawMalloc`, :c:func:`PyMem_RawRealloc` or :c:func:"
"`PyMem_RawCalloc`."
msgstr ""
#: ../Doc/c-api/memory.rst:146
msgid ""
"If the request fails, :c:func:`PyMem_RawRealloc` returns *NULL* and *p* "
"remains a valid pointer to the previous memory area."
msgstr ""
#: ../Doc/c-api/memory.rst:152
msgid ""
"Frees the memory block pointed to by *p*, which must have been returned by a "
"previous call to :c:func:`PyMem_RawMalloc`, :c:func:`PyMem_RawRealloc` or :c:"
"func:`PyMem_RawCalloc`. Otherwise, or if ``PyMem_RawFree(p)`` has been "
"called before, undefined behavior occurs."
msgstr ""
#: ../Doc/c-api/memory.rst:157 ../Doc/c-api/memory.rst:227
#: ../Doc/c-api/memory.rst:329
msgid "If *p* is *NULL*, no operation is performed."
msgstr ""
#: ../Doc/c-api/memory.rst:163
msgid "Memory Interface"
msgstr ""
#: ../Doc/c-api/memory.rst:165 ../Doc/c-api/memory.rst:271
msgid ""
"The following function sets, modeled after the ANSI C standard, but "
"specifying behavior when requesting zero bytes, are available for allocating "
"and releasing memory from the Python heap."
msgstr ""
#: ../Doc/c-api/memory.rst:169
msgid ""
"The :ref:`default memory allocator <default-memory-allocators>` uses the :"
"ref:`pymalloc memory allocator <pymalloc>`."
msgstr ""
#: ../Doc/c-api/memory.rst:174 ../Doc/c-api/memory.rst:280
msgid ""
"The :term:`GIL <global interpreter lock>` must be held when using these "
"functions."
msgstr ""
#: ../Doc/c-api/memory.rst:179
msgid ""
"The default allocator is now pymalloc instead of system :c:func:`malloc`."
msgstr ""
#: ../Doc/c-api/memory.rst:186
msgid ""
"Requesting zero bytes returns a distinct non-*NULL* pointer if possible, as "
"if ``PyMem_Malloc(1)`` had been called instead. The memory will not have "
"been initialized in any way."
msgstr ""
#: ../Doc/c-api/memory.rst:197
msgid ""
"Requesting zero elements or elements of size zero bytes returns a distinct "
"non-*NULL* pointer if possible, as if ``PyMem_Calloc(1, 1)`` had been called "
"instead."
msgstr ""
#: ../Doc/c-api/memory.rst:209
msgid ""
"If *p* is *NULL*, the call is equivalent to ``PyMem_Malloc(n)``; else if *n* "
"is equal to zero, the memory block is resized but is not freed, and the "
"returned pointer is non-*NULL*."
msgstr ""
#: ../Doc/c-api/memory.rst:213
msgid ""
"Unless *p* is *NULL*, it must have been returned by a previous call to :c:"
"func:`PyMem_Malloc`, :c:func:`PyMem_Realloc` or :c:func:`PyMem_Calloc`."
msgstr ""
#: ../Doc/c-api/memory.rst:216
msgid ""
"If the request fails, :c:func:`PyMem_Realloc` returns *NULL* and *p* remains "
"a valid pointer to the previous memory area."
msgstr ""
#: ../Doc/c-api/memory.rst:222
msgid ""
"Frees the memory block pointed to by *p*, which must have been returned by a "
"previous call to :c:func:`PyMem_Malloc`, :c:func:`PyMem_Realloc` or :c:func:"
"`PyMem_Calloc`. Otherwise, or if ``PyMem_Free(p)`` has been called before, "
"undefined behavior occurs."
msgstr ""
#: ../Doc/c-api/memory.rst:229
msgid ""
"The following type-oriented macros are provided for convenience. Note that "
"*TYPE* refers to any C type."
msgstr ""
#: ../Doc/c-api/memory.rst:235
msgid ""
"Same as :c:func:`PyMem_Malloc`, but allocates ``(n * sizeof(TYPE))`` bytes "
"of memory. Returns a pointer cast to :c:type:`TYPE\\*`. The memory will "
"not have been initialized in any way."
msgstr ""
#: ../Doc/c-api/memory.rst:242
msgid ""
"Same as :c:func:`PyMem_Realloc`, but the memory block is resized to ``(n * "
"sizeof(TYPE))`` bytes. Returns a pointer cast to :c:type:`TYPE\\*`. On "
"return, *p* will be a pointer to the new memory area, or *NULL* in the event "
"of failure."
msgstr ""
#: ../Doc/c-api/memory.rst:247
msgid ""
"This is a C preprocessor macro; *p* is always reassigned. Save the original "
"value of *p* to avoid losing memory when handling errors."
msgstr ""
#: ../Doc/c-api/memory.rst:253
msgid "Same as :c:func:`PyMem_Free`."
msgstr ""
#: ../Doc/c-api/memory.rst:255
msgid ""
"In addition, the following macro sets are provided for calling the Python "
"memory allocator directly, without involving the C API functions listed "
"above. However, note that their use does not preserve binary compatibility "
"across Python versions and is therefore deprecated in extension modules."
msgstr ""
#: ../Doc/c-api/memory.rst:260
msgid "``PyMem_MALLOC(size)``"
msgstr ""
#: ../Doc/c-api/memory.rst:261
msgid "``PyMem_NEW(type, size)``"
msgstr ""
#: ../Doc/c-api/memory.rst:262
msgid "``PyMem_REALLOC(ptr, size)``"
msgstr ""
#: ../Doc/c-api/memory.rst:263
msgid "``PyMem_RESIZE(ptr, type, size)``"
msgstr ""
#: ../Doc/c-api/memory.rst:264
msgid "``PyMem_FREE(ptr)``"
msgstr ""
#: ../Doc/c-api/memory.rst:265
msgid "``PyMem_DEL(ptr)``"
msgstr ""
#: ../Doc/c-api/memory.rst:269
msgid "Object allocators"
msgstr ""
#: ../Doc/c-api/memory.rst:275
msgid ""
"The :ref:`default object allocator <default-memory-allocators>` uses the :"
"ref:`pymalloc memory allocator <pymalloc>`."
msgstr ""
#: ../Doc/c-api/memory.rst:288
msgid ""
"Requesting zero bytes returns a distinct non-*NULL* pointer if possible, as "
"if ``PyObject_Malloc(1)`` had been called instead. The memory will not have "
"been initialized in any way."
msgstr ""
#: ../Doc/c-api/memory.rst:299
msgid ""
"Requesting zero elements or elements of size zero bytes returns a distinct "
"non-*NULL* pointer if possible, as if ``PyObject_Calloc(1, 1)`` had been "
"called instead."
msgstr ""
#: ../Doc/c-api/memory.rst:311
msgid ""
"If *p* is *NULL*, the call is equivalent to ``PyObject_Malloc(n)``; else if "
"*n* is equal to zero, the memory block is resized but is not freed, and the "
"returned pointer is non-*NULL*."
msgstr ""
#: ../Doc/c-api/memory.rst:315
msgid ""
"Unless *p* is *NULL*, it must have been returned by a previous call to :c:"
"func:`PyObject_Malloc`, :c:func:`PyObject_Realloc` or :c:func:"
"`PyObject_Calloc`."
msgstr ""
#: ../Doc/c-api/memory.rst:318
msgid ""
"If the request fails, :c:func:`PyObject_Realloc` returns *NULL* and *p* "
"remains a valid pointer to the previous memory area."
msgstr ""
#: ../Doc/c-api/memory.rst:324
msgid ""
"Frees the memory block pointed to by *p*, which must have been returned by a "
"previous call to :c:func:`PyObject_Malloc`, :c:func:`PyObject_Realloc` or :c:"
"func:`PyObject_Calloc`. Otherwise, or if ``PyObject_Free(p)`` has been "
"called before, undefined behavior occurs."
msgstr ""
#: ../Doc/c-api/memory.rst:335
msgid "Default Memory Allocators"
msgstr ""
#: ../Doc/c-api/memory.rst:337
msgid "Default memory allocators:"
msgstr ""
#: ../Doc/c-api/memory.rst:340
msgid "Configuration"
msgstr ""
#: ../Doc/c-api/memory.rst:340
msgid "Name"
msgstr ""
#: ../Doc/c-api/memory.rst:340
msgid "PyMem_RawMalloc"
msgstr ""
#: ../Doc/c-api/memory.rst:340
msgid "PyMem_Malloc"
msgstr ""
#: ../Doc/c-api/memory.rst:340
msgid "PyObject_Malloc"
msgstr ""
#: ../Doc/c-api/memory.rst:342
msgid "Release build"
msgstr ""
#: ../Doc/c-api/memory.rst:342
msgid "``\"pymalloc\"``"
msgstr ""
#: ../Doc/c-api/memory.rst:342 ../Doc/c-api/memory.rst:344
msgid "``malloc``"
msgstr ""
#: ../Doc/c-api/memory.rst:342
msgid "``pymalloc``"
msgstr ""
#: ../Doc/c-api/memory.rst:343
msgid "Debug build"
msgstr ""
#: ../Doc/c-api/memory.rst:343
msgid "``\"pymalloc_debug\"``"
msgstr ""
#: ../Doc/c-api/memory.rst:343 ../Doc/c-api/memory.rst:345
msgid "``malloc`` + debug"
msgstr ""
#: ../Doc/c-api/memory.rst:343
msgid "``pymalloc`` + debug"
msgstr ""
#: ../Doc/c-api/memory.rst:344
msgid "Release build, without pymalloc"
msgstr ""
#: ../Doc/c-api/memory.rst:344
msgid "``\"malloc\"``"
msgstr ""
#: ../Doc/c-api/memory.rst:345
msgid "Debug build, without pymalloc"
msgstr ""
#: ../Doc/c-api/memory.rst:345
msgid "``\"malloc_debug\"``"
msgstr ""
#: ../Doc/c-api/memory.rst:348
msgid "Legend:"
msgstr ""
#: ../Doc/c-api/memory.rst:350
msgid "Name: value for :envvar:`PYTHONMALLOC` environment variable"
msgstr ""
#: ../Doc/c-api/memory.rst:351
msgid ""
"``malloc``: system allocators from the standard C library, C functions: :c:"
"func:`malloc`, :c:func:`calloc`, :c:func:`realloc` and :c:func:`free`"
msgstr ""
#: ../Doc/c-api/memory.rst:353
msgid "``pymalloc``: :ref:`pymalloc memory allocator <pymalloc>`"
msgstr ""
#: ../Doc/c-api/memory.rst:354
msgid ""
"\"+ debug\": with debug hooks installed by :c:func:`PyMem_SetupDebugHooks`"
msgstr ""
#: ../Doc/c-api/memory.rst:358
msgid "Customize Memory Allocators"
msgstr ""
#: ../Doc/c-api/memory.rst:364
msgid ""
"Structure used to describe a memory block allocator. The structure has four "
"fields:"
msgstr ""
#: ../Doc/c-api/memory.rst:368 ../Doc/c-api/memory.rst:513
msgid "Field"
msgstr ""
#: ../Doc/c-api/memory.rst:368 ../Doc/c-api/memory.rst:513
msgid "Meaning"
msgstr ""
#: ../Doc/c-api/memory.rst:370 ../Doc/c-api/memory.rst:515
msgid "``void *ctx``"
msgstr ""
#: ../Doc/c-api/memory.rst:370 ../Doc/c-api/memory.rst:515
msgid "user context passed as first argument"
msgstr ""
#: ../Doc/c-api/memory.rst:372
msgid "``void* malloc(void *ctx, size_t size)``"
msgstr ""
#: ../Doc/c-api/memory.rst:372
msgid "allocate a memory block"
msgstr ""
#: ../Doc/c-api/memory.rst:374
msgid "``void* calloc(void *ctx, size_t nelem, size_t elsize)``"
msgstr ""
#: ../Doc/c-api/memory.rst:374
msgid "allocate a memory block initialized with zeros"
msgstr ""
#: ../Doc/c-api/memory.rst:377
msgid "``void* realloc(void *ctx, void *ptr, size_t new_size)``"
msgstr ""
#: ../Doc/c-api/memory.rst:377
msgid "allocate or resize a memory block"
msgstr ""
#: ../Doc/c-api/memory.rst:379
msgid "``void free(void *ctx, void *ptr)``"
msgstr ""
#: ../Doc/c-api/memory.rst:379
msgid "free a memory block"
msgstr ""
#: ../Doc/c-api/memory.rst:382
msgid ""
"The :c:type:`PyMemAllocator` structure was renamed to :c:type:"
"`PyMemAllocatorEx` and a new ``calloc`` field was added."
msgstr ""
#: ../Doc/c-api/memory.rst:389
msgid "Enum used to identify an allocator domain. Domains:"
msgstr ""
#: ../Doc/c-api/memory.rst:393 ../Doc/c-api/memory.rst:402
#: ../Doc/c-api/memory.rst:411
msgid "Functions:"
msgstr ""
#: ../Doc/c-api/memory.rst:395
msgid ":c:func:`PyMem_RawMalloc`"
msgstr ""
#: ../Doc/c-api/memory.rst:396
msgid ":c:func:`PyMem_RawRealloc`"
msgstr ""
#: ../Doc/c-api/memory.rst:397
msgid ":c:func:`PyMem_RawCalloc`"
msgstr ""
#: ../Doc/c-api/memory.rst:398
msgid ":c:func:`PyMem_RawFree`"
msgstr ""
#: ../Doc/c-api/memory.rst:404
msgid ":c:func:`PyMem_Malloc`,"
msgstr ""
#: ../Doc/c-api/memory.rst:405
msgid ":c:func:`PyMem_Realloc`"
msgstr ""
#: ../Doc/c-api/memory.rst:406
msgid ":c:func:`PyMem_Calloc`"
msgstr ""
#: ../Doc/c-api/memory.rst:407
msgid ":c:func:`PyMem_Free`"
msgstr ""
#: ../Doc/c-api/memory.rst:413
msgid ":c:func:`PyObject_Malloc`"
msgstr ""
#: ../Doc/c-api/memory.rst:414
msgid ":c:func:`PyObject_Realloc`"
msgstr ""
#: ../Doc/c-api/memory.rst:415
msgid ":c:func:`PyObject_Calloc`"
msgstr ""
#: ../Doc/c-api/memory.rst:416
msgid ":c:func:`PyObject_Free`"
msgstr ""
#: ../Doc/c-api/memory.rst:420
msgid "Get the memory block allocator of the specified domain."
msgstr ""
#: ../Doc/c-api/memory.rst:425
msgid "Set the memory block allocator of the specified domain."
msgstr ""
#: ../Doc/c-api/memory.rst:427
msgid ""
"The new allocator must return a distinct non-NULL pointer when requesting "
"zero bytes."
msgstr ""
#: ../Doc/c-api/memory.rst:430
msgid ""
"For the :c:data:`PYMEM_DOMAIN_RAW` domain, the allocator must be thread-"
"safe: the :term:`GIL <global interpreter lock>` is not held when the "
"allocator is called."
msgstr ""
#: ../Doc/c-api/memory.rst:434
msgid ""
"If the new allocator is not a hook (does not call the previous allocator), "
"the :c:func:`PyMem_SetupDebugHooks` function must be called to reinstall the "
"debug hooks on top on the new allocator."
msgstr ""
#: ../Doc/c-api/memory.rst:441
msgid "Setup hooks to detect bugs in the Python memory allocator functions."
msgstr ""
#: ../Doc/c-api/memory.rst:443
msgid ""
"Newly allocated memory is filled with the byte ``0xCD`` (``CLEANBYTE``), "
"freed memory is filled with the byte ``0xDD`` (``DEADBYTE``). Memory blocks "
"are surrounded by \"forbidden bytes\" (``FORBIDDENBYTE``: byte ``0xFD``)."
msgstr ""
#: ../Doc/c-api/memory.rst:447
msgid "Runtime checks:"
msgstr ""
#: ../Doc/c-api/memory.rst:449
msgid ""
"Detect API violations, ex: :c:func:`PyObject_Free` called on a buffer "
"allocated by :c:func:`PyMem_Malloc`"
msgstr ""
#: ../Doc/c-api/memory.rst:451
msgid "Detect write before the start of the buffer (buffer underflow)"
msgstr ""
#: ../Doc/c-api/memory.rst:452
msgid "Detect write after the end of the buffer (buffer overflow)"
msgstr ""
#: ../Doc/c-api/memory.rst:453
msgid ""
"Check that the :term:`GIL <global interpreter lock>` is held when allocator "
"functions of :c:data:`PYMEM_DOMAIN_OBJ` (ex: :c:func:`PyObject_Malloc`) and :"
"c:data:`PYMEM_DOMAIN_MEM` (ex: :c:func:`PyMem_Malloc`) domains are called"
msgstr ""
#: ../Doc/c-api/memory.rst:458
msgid ""
"On error, the debug hooks use the :mod:`tracemalloc` module to get the "
"traceback where a memory block was allocated. The traceback is only "
"displayed if :mod:`tracemalloc` is tracing Python memory allocations and the "
"memory block was traced."
msgstr ""
#: ../Doc/c-api/memory.rst:463
msgid ""
"These hooks are :ref:`installed by default <default-memory-allocators>` if "
"Python is compiled in debug mode. The :envvar:`PYTHONMALLOC` environment "
"variable can be used to install debug hooks on a Python compiled in release "
"mode."
msgstr ""
#: ../Doc/c-api/memory.rst:468
msgid ""
"This function now also works on Python compiled in release mode. On error, "
"the debug hooks now use :mod:`tracemalloc` to get the traceback where a "
"memory block was allocated. The debug hooks now also check if the GIL is "
"held when functions of :c:data:`PYMEM_DOMAIN_OBJ` and :c:data:"
"`PYMEM_DOMAIN_MEM` domains are called."
msgstr ""
#: ../Doc/c-api/memory.rst:475
msgid ""
"Byte patterns ``0xCB`` (``CLEANBYTE``), ``0xDB`` (``DEADBYTE``) and ``0xFB`` "
"(``FORBIDDENBYTE``) have been replaced with ``0xCD``, ``0xDD`` and ``0xFD`` "
"to use the same values than Windows CRT debug ``malloc()`` and ``free()``."
msgstr ""
#: ../Doc/c-api/memory.rst:485
msgid "The pymalloc allocator"
msgstr ""
#: ../Doc/c-api/memory.rst:487
msgid ""
"Python has a *pymalloc* allocator optimized for small objects (smaller or "
"equal to 512 bytes) with a short lifetime. It uses memory mappings called "
"\"arenas\" with a fixed size of 256 KiB. It falls back to :c:func:"
"`PyMem_RawMalloc` and :c:func:`PyMem_RawRealloc` for allocations larger than "
"512 bytes."
msgstr ""
#: ../Doc/c-api/memory.rst:492
msgid ""
"*pymalloc* is the :ref:`default allocator <default-memory-allocators>` of "
"the :c:data:`PYMEM_DOMAIN_MEM` (ex: :c:func:`PyMem_Malloc`) and :c:data:"
"`PYMEM_DOMAIN_OBJ` (ex: :c:func:`PyObject_Malloc`) domains."
msgstr ""
#: ../Doc/c-api/memory.rst:496
msgid "The arena allocator uses the following functions:"
msgstr ""
#: ../Doc/c-api/memory.rst:498
msgid ":c:func:`VirtualAlloc` and :c:func:`VirtualFree` on Windows,"
msgstr ""
#: ../Doc/c-api/memory.rst:499
msgid ":c:func:`mmap` and :c:func:`munmap` if available,"
msgstr ""
#: ../Doc/c-api/memory.rst:500
msgid ":c:func:`malloc` and :c:func:`free` otherwise."
msgstr ""
#: ../Doc/c-api/memory.rst:503
msgid "Customize pymalloc Arena Allocator"
msgstr ""
#: ../Doc/c-api/memory.rst:509
msgid ""
"Structure used to describe an arena allocator. The structure has three "
"fields:"
msgstr ""
#: ../Doc/c-api/memory.rst:517
msgid "``void* alloc(void *ctx, size_t size)``"
msgstr ""
#: ../Doc/c-api/memory.rst:517
msgid "allocate an arena of size bytes"
msgstr ""
#: ../Doc/c-api/memory.rst:519
msgid "``void free(void *ctx, size_t size, void *ptr)``"
msgstr ""
#: ../Doc/c-api/memory.rst:519
msgid "free an arena"
msgstr ""
#: ../Doc/c-api/memory.rst:524
msgid "Get the arena allocator."
msgstr ""
#: ../Doc/c-api/memory.rst:528
msgid "Set the arena allocator."
msgstr ""
#: ../Doc/c-api/memory.rst:532
msgid "tracemalloc C API"
msgstr ""
#: ../Doc/c-api/memory.rst:556
msgid "Examples"
msgstr ""
#: ../Doc/c-api/memory.rst:558
msgid ""
"Here is the example from section :ref:`memoryoverview`, rewritten so that "
"the I/O buffer is allocated from the Python heap by using the first function "
"set::"
msgstr ""
#: ../Doc/c-api/memory.rst:571
msgid "The same code using the type-oriented function set::"
msgstr ""
#: ../Doc/c-api/memory.rst:583
msgid ""
"Note that in the two examples above, the buffer is always manipulated via "
"functions belonging to the same set. Indeed, it is required to use the same "
"memory API family for a given memory block, so that the risk of mixing "
"different allocators is reduced to a minimum. The following code sequence "
"contains two errors, one of which is labeled as *fatal* because it mixes two "
"different allocators operating on different heaps. ::"
msgstr ""
#: ../Doc/c-api/memory.rst:598
msgid ""
"In addition to the functions aimed at handling raw memory blocks from the "
"Python heap, objects in Python are allocated and released with :c:func:"
"`PyObject_New`, :c:func:`PyObject_NewVar` and :c:func:`PyObject_Del`."
msgstr ""
#: ../Doc/c-api/memory.rst:602
msgid ""
"These will be explained in the next chapter on defining and implementing new "
"object types in C."
msgstr ""