-
-
Notifications
You must be signed in to change notification settings - Fork 98
Expand file tree
/
Copy pathmemory.po
More file actions
1470 lines (1251 loc) · 62.7 KB
/
memory.po
File metadata and controls
1470 lines (1251 loc) · 62.7 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
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001 Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# python-doc bot, 2026
# 99 <wh2099@pm.me>, 2026
# Freesand Leo <yuqinju@163.com>, 2026
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.15\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-05-08 18:34+0000\n"
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
"Last-Translator: Freesand Leo <yuqinju@163.com>, 2026\n"
"Language-Team: Chinese (China) (https://app.transifex.com/python-doc/teams/5390/zh_CN/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: zh_CN\n"
"Plural-Forms: nplurals=1; plural=0;\n"
#: ../../c-api/memory.rst:8
msgid "Memory Management"
msgstr "内存管理"
#: ../../c-api/memory.rst:13
msgid "Overview"
msgstr "概述"
#: ../../c-api/memory.rst:15
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 ""
"在 Python 中,内存管理涉及到一个包含所有 Python 对象和数据结构的私有堆(heap)。这个私有堆的管理由内部的 *Python "
"内存管理器(Python memory manager)* 保证。Python "
"内存管理器有不同的组件来处理各种动态存储管理方面的问题,如共享、分割、预分配或缓存。"
#: ../../c-api/memory.rst:21
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 ""
"在最底层,一个原始内存分配器通过与操作系统的内存管理器交互,确保私有堆中有足够的空间来存储所有与 Python "
"相关的数据。在原始内存分配器的基础上,几个对象特定的分配器在同一堆上运行,并根据每种对象类型的特点实现不同的内存管理策略。例如,整数对象在堆内的管理方式不同于字符串、元组或字典,因为整数需要不同的存储需求和速度与空间的权衡。因此,Python"
" 内存管理器将一些工作分配给对象特定分配器,但确保后者在私有堆的范围内运行。"
#: ../../c-api/memory.rst:32
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 ""
"Python 堆内存的管理是由解释器来执行,用户对它没有控制权,即使他们经常操作指向堆内内存块的对象指针,理解这一点十分重要。Python "
"对象和其他内部缓冲区的堆空间分配是由 Python 内存管理器按需通过本文档中列出的 Python/C API 函数进行的。"
#: ../../c-api/memory.rst:45
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 ""
"为了避免内存破坏,扩展的作者永远不应该试图用 C 库函数导出的函数来对 Python 对象进行操作,这些函数包括: :c:func:`malloc`, "
":c:func:`calloc`, :c:func:`realloc` 和 :c:func:`free`。这将导致 C 分配器和 Python "
"内存管理器之间的混用,引发严重后果,这是由于它们实现了不同的算法,并在不同的堆上操作。但是,我们可以安全地使用 C "
"库分配器为单独的目的分配和释放内存块,如下例所示:"
#: ../../c-api/memory.rst:54
msgid ""
"PyObject *res;\n"
"char *buf = (char *) malloc(BUFSIZ); /* for I/O */\n"
"\n"
"if (buf == NULL)\n"
" return PyErr_NoMemory();\n"
"...Do some I/O operation involving buf...\n"
"res = PyBytes_FromString(buf);\n"
"free(buf); /* malloc'ed */\n"
"return res;"
msgstr ""
"PyObject *res;\n"
"char *buf = (char *) malloc(BUFSIZ); /* for I/O */\n"
"\n"
"if (buf == NULL)\n"
" return PyErr_NoMemory();\n"
"...执行一些涉及 buf 的 I/O 操作...\n"
"res = PyBytes_FromString(buf);\n"
"free(buf); /* 已分配的 */\n"
"return res;"
#: ../../c-api/memory.rst:64
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 bytes object returned as a result."
msgstr "在这个例子中,I/O 缓冲区的内存请求是由 C 库分配器处理的。Python 内存管理器只参与了分配作为结果返回的字节对象。"
#: ../../c-api/memory.rst:68
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 ""
"然而,在大多数情况下,都建议专门基于 Python 堆来分配内存,因为后者是由 Python 内存管理器控制的。例如,当解释器使用 C "
"编写的新对象类型进行扩展时就必须这样做。使用 Python 堆的另一个理由是需要能 *通知* Python "
"内存管理器有关扩展模块的内存需求。即使所请求的内存全部只用于内部的、高度特定的目的,将所有的内存请求交给 Python "
"内存管理器能让解释器对其内存占用的整体情况有更准确的了解。 因此,在特定情况下,Python "
"内存管理器可能会触发或不触发适当的操作,如垃圾回收、内存压缩或其他的预防性操作。请注意通过使用前面例子所演示的 C 库分配器,为 I/O "
"缓冲区分配的内存将完全不受 Python 内存管理器的控制。"
#: ../../c-api/memory.rst:84
msgid ""
"The :envvar:`PYTHONMALLOC` environment variable can be used to configure the"
" memory allocators used by Python."
msgstr "环境变量 :envvar:`PYTHONMALLOC` 可被用来配置 Python 所使用的内存分配器。"
#: ../../c-api/memory.rst:87
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 ""
"环境变量 :envvar:`PYTHONMALLOCSTATS` 可以用来在每次创建新的 pymalloc 对象区域时以及在关闭时打印 "
":ref:`pymalloc 内存分配器 <pymalloc>` 的统计数据。"
#: ../../c-api/memory.rst:92
msgid "Allocator Domains"
msgstr "分配器域"
#: ../../c-api/memory.rst:96
msgid ""
"All allocating functions belong to one of three different \"domains\" (see "
"also :c:type:`PyMemAllocatorDomain`). These domains represent different "
"allocation strategies and are optimized for different purposes. The specific"
" details on how every domain allocates memory or what internal functions "
"each domain calls is considered an implementation detail, but for debugging "
"purposes a simplified table can be found at :ref:`default-memory-"
"allocators`. The APIs used to allocate and free a block of memory must be "
"from the same domain. For example, :c:func:`PyMem_Free` must be used to free"
" memory allocated using :c:func:`PyMem_Malloc`."
msgstr ""
"所有分配函数都归属于三个不同的“域”之一 (另请参阅 :c:type:`PyMemAllocatorDomain`)。 "
"这些域代表不同的分配策略并针对不同的目的进行了优化。每个域如何分配内存以及每个域会调用哪些内部函数的详情被认为是实现细节,但是出于调试目的可以在 "
":ref:`default-memory-allocators` 找到一张简化的表格。用于分配和释放内存的 API "
"必须来自同一个域。例如,:c:func:`PyMem_Free` 必须被用来释放使用 :c:func:`PyMem_Malloc` 分配的内存。"
#: ../../c-api/memory.rst:105
msgid "The three allocation domains are:"
msgstr "三个分配域分别是:"
#: ../../c-api/memory.rst:107
msgid ""
"Raw domain: intended for allocating memory for general-purpose memory "
"buffers where the allocation *must* go to the system allocator or where the "
"allocator can operate without an :term:`attached thread state`. The memory "
"is requested directly from the system. See :ref:`Raw Memory Interface <raw-"
"memoryinterface>`."
msgstr ""
"原始域:用于为通用内存缓冲区分配内存,其分配 *必须* 转到系统分配器或者可在没有 :term:`attached thread state` "
"的情况下使用的分配器。内存将直接自系统请求。参见 :ref:`原始内存接口 <raw-memoryinterface>`。"
#: ../../c-api/memory.rst:112
msgid ""
"\"Mem\" domain: intended for allocating memory for Python buffers and "
"general-purpose memory buffers where the allocation must be performed with "
"an :term:`attached thread state`. The memory is taken from the Python "
"private heap. See :ref:`Memory Interface <memoryinterface>`."
msgstr ""
"“内存”域:用于为 Python 缓冲区和通用内存缓冲区分配内存,其分配必须在具有 :term:`attached thread state` "
"的情况下进行。内存将从 Python 私有堆获取。参见 :ref:`内存接口 <memoryinterface>`。"
#: ../../c-api/memory.rst:117
msgid ""
"Object domain: intended for allocating memory for Python objects. The memory"
" is taken from the Python private heap. See :ref:`Object allocators "
"<objectinterface>`."
msgstr ""
"对象域:用于为 Python 对象分配内存。内存将从 Python 私有堆获取。参见 :ref:`对象分配器 <objectinterface>`。"
#: ../../c-api/memory.rst:122
msgid ""
"The :term:`free-threaded <free threading>` build requires that only Python "
"objects are allocated using the \"object\" domain and that all Python "
"objects are allocated using that domain. This differs from the prior Python "
"versions, where this was only a best practice and not a hard requirement."
msgstr ""
":term:`自由线程 <free threading>` 构建版要求仅 Python 对象使用\"对象\"域来分配并且所有 Python "
"对象都使用该域来分配。这不同于之前的 Python 版本,在之前版本中这只是最佳实践而非硬性要求。"
#: ../../c-api/memory.rst:126
msgid ""
"For example, buffers (non-Python objects) should be allocated using "
":c:func:`PyMem_Malloc`, :c:func:`PyMem_RawMalloc`, or :c:func:`malloc`, but "
"not :c:func:`PyObject_Malloc`."
msgstr ""
"例如,缓冲区(非 Python 对象)的分配应当使用 :c:func:`PyMem_Malloc`, :c:func:`PyMem_RawMalloc`"
" 或 :c:func:`malloc`,而不能用 :c:func:`PyObject_Malloc`。"
#: ../../c-api/memory.rst:129
msgid "See :ref:`Memory Allocation APIs <free-threaded-memory-allocation>`."
msgstr "参见 :ref:`内存分配 API <free-threaded-memory-allocation>`。"
#: ../../c-api/memory.rst:135
msgid "Raw Memory Interface"
msgstr "原始内存接口"
#: ../../c-api/memory.rst:137
msgid ""
"The following function sets are wrappers to the system allocator. These "
"functions are thread-safe, so a :term:`thread state` does not need to be "
":term:`attached <attached thread state>`."
msgstr ""
"以下函数集是系统分配器的包装器。这些函数是线程安全的,因此不需要 :term:`附加 <attached thread state>` "
":term:`thread state` 对象。"
#: ../../c-api/memory.rst:141
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 ""
":ref:`默认原始内存分配器 <default-memory-allocators>` 使用以下函数::c:func:`malloc`, "
":c:func:`calloc`, :c:func:`realloc` 和 :c:func:`!free`;当请求零个字节时则调用 "
"``malloc(1)`` (或 ``calloc(1, 1)``)。"
#: ../../c-api/memory.rst:150 ../../c-api/memory.rst:228
#: ../../c-api/memory.rst:361
msgid ""
"Allocates *n* bytes and returns a pointer of type :c:expr:`void*` to the "
"allocated memory, or ``NULL`` if the request fails."
msgstr "分配 *n* 个字节并返回一个指向所分配内存的 :c:expr:`void*` 类型指针,如果请求失败则返回 ``NULL``。"
#: ../../c-api/memory.rst:153
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 ""
"请求零字节可能返回一个独特的非 ``NULL`` 指针,就像调用了 ``PyMem_RawMalloc(1)`` 一样。但是内存不会以任何方式被初始化。"
#: ../../c-api/memory.rst:160 ../../c-api/memory.rst:238
#: ../../c-api/memory.rst:371
msgid ""
"Allocates *nelem* elements each whose size in bytes is *elsize* and returns "
"a pointer of type :c:expr:`void*` to the allocated memory, or ``NULL`` if "
"the request fails. The memory is initialized to zeros."
msgstr ""
"分配 *nelem* 个元素,每个元素的大小为 *elsize* 个字节,并返回指向所分配的内存的 :c:expr:`void*` "
"类型指针,如果请求失败则返回 ``NULL``。内存会被初始化为零。"
#: ../../c-api/memory.rst:164
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 "请求零字节可能返回一个独特的非 ``NULL`` 指针,就像调用了 ``PyMem_RawCalloc(1, 1)`` 一样。"
#: ../../c-api/memory.rst:173 ../../c-api/memory.rst:251
#: ../../c-api/memory.rst:384
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 "将 *p* 指向的内存块大小调整为 *n* 字节。以新旧内存块大小中的最小值为准,其中内容保持不变,"
#: ../../c-api/memory.rst:176
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 ""
"如果 *p* 是 ``NULL``,则相当于调用 ``PyMem_RawMalloc(n)``;如果 *n* 等于 "
"0,则内存块大小会被调整,但不会被释放,返回非 ``NULL`` 指针。"
#: ../../c-api/memory.rst:180
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 ""
"除非 *p* 是 ``NULL``,否则它必须是之前调用 "
":c:func:`PyMem_RawMalloc`、:c:func:`PyMem_RawRealloc` 或 "
":c:func:`PyMem_RawCalloc` 所返回的。"
#: ../../c-api/memory.rst:184
msgid ""
"If the request fails, :c:func:`PyMem_RawRealloc` returns ``NULL`` and *p* "
"remains a valid pointer to the previous memory area."
msgstr "如果请求失败,:c:func:`PyMem_RawRealloc` 返回 ``NULL``,*p* 仍然是指向先前内存区域的有效指针。"
#: ../../c-api/memory.rst:190
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 ""
"释放 *p* 指向的内存块。*p* 必须是之前调用 "
":c:func:`PyMem_RawMalloc`、:c:func:`PyMem_RawRealloc` 或 "
":c:func:`PyMem_RawCalloc` 所返回的指针。否则,或在 ``PyMem_RawFree(p)`` "
"之前已经调用过的情况下,未定义的行为会发生。"
#: ../../c-api/memory.rst:195 ../../c-api/memory.rst:272
#: ../../c-api/memory.rst:405
msgid "If *p* is ``NULL``, no operation is performed."
msgstr "如果 *p* 是 ``NULL``, 那么什么操作也不会进行。"
#: ../../c-api/memory.rst:201
msgid "Memory Interface"
msgstr "内存接口"
#: ../../c-api/memory.rst:203 ../../c-api/memory.rst:340
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 "以下函数集,仿照 ANSI C 标准,并指定了请求零字节时的行为,可用于从 Python 堆分配和释放内存。"
#: ../../c-api/memory.rst:207
msgid ""
"In the GIL-enabled build (default build) the :ref:`default memory allocator "
"<default-memory-allocators>` uses the :ref:`pymalloc memory allocator "
"<pymalloc>`, whereas in the :term:`free-threaded build`, the default is the "
":ref:`mimalloc memory allocator <mimalloc>` instead."
msgstr ""
"在启用 GIL 的构建(默认构建)上 :ref:`默认内存分配器 <default-memory-allocators>` 使用 "
":ref:`pymalloc 内存分配器 <pymalloc>`,而在 :term:`free-threaded build` 上,默认改用 "
":ref:`mimalloc 内存分配器 <mimalloc>`。"
#: ../../c-api/memory.rst:215 ../../c-api/memory.rst:357
msgid ""
"There must be an :term:`attached thread state` when using these functions."
msgstr "在使用这些函数时必须有一个 :term:`attached thread state`。"
#: ../../c-api/memory.rst:219
msgid ""
"The default allocator is now pymalloc instead of system :c:func:`malloc`."
msgstr "现在默认的分配器是 pymalloc 而非系统的 :c:func:`malloc` 函数。"
#: ../../c-api/memory.rst:223
msgid ""
"In the :term:`free-threaded <free threading>` build, the default allocator "
"is now :ref:`mimalloc <mimalloc>`."
msgstr ""
"在 :term:`free-threaded <free threading>` 构建上,现在默认的分配器是 :ref:`mimalloc "
"<mimalloc>`。"
#: ../../c-api/memory.rst:231
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 ""
"请求零字节可能返回一个独特的非 ``NULL`` 指针,就像调用了 ``PyMem_Malloc(1)`` 一样。但是内存不会以任何方式被初始化。"
#: ../../c-api/memory.rst:242
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 "请求零字节可能返回一个独特的非 ``NULL`` 指针,就像调用了 ``PyMem_Calloc(1, 1)`` 一样。"
#: ../../c-api/memory.rst:254
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 ""
"如果 *p* 是 ``NULL``,则相当于调用 ``PyMem_Malloc(n)``;如果 *n* 等于 "
"0,则内存块大小会被调整,但不会被释放,返回非 ``NULL`` 指针。"
#: ../../c-api/memory.rst:258
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 ""
"除非 *p* 是 ``NULL``,否则它必须是之前调用 :c:func:`PyMem_Malloc`、:c:func:`PyMem_Realloc` "
"或 :c:func:`PyMem_Calloc` 所返回的。"
#: ../../c-api/memory.rst:261
msgid ""
"If the request fails, :c:func:`PyMem_Realloc` returns ``NULL`` and *p* "
"remains a valid pointer to the previous memory area."
msgstr "如果请求失败,:c:func:`PyMem_Realloc` 返回 ``NULL``,*p* 仍然是指向先前内存区域的有效指针。"
#: ../../c-api/memory.rst:267
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 ""
"释放 *p* 指向的内存块。*p* 必须是之前调用 :c:func:`PyMem_Malloc`、:c:func:`PyMem_Realloc` 或 "
":c:func:`PyMem_Calloc` 所返回的指针。否则,或在 ``PyMem_Free(p)`` 之前已经调用过的情况下,未定义的行为会发生。"
#: ../../c-api/memory.rst:274
msgid ""
"The following type-oriented macros are provided for convenience. Note that"
" *TYPE* refers to any C type."
msgstr "以下面向类型的宏为方便而提供。注意 *TYPE* 可以指任何 C 类型。"
#: ../../c-api/memory.rst:280
msgid ""
"Same as :c:func:`PyMem_Malloc`, but allocates ``(n * sizeof(TYPE))`` bytes "
"of memory. Returns a pointer cast to ``TYPE*``. The memory will not have "
"been initialized in any way."
msgstr ""
"与 :c:func:`PyMem_Malloc` 相同,但会分配 ``(n * sizeof(TYPE))`` 字节的内存。返回一个转换为 "
"``TYPE*`` 的指针。内存不会以任何方式被初始化。"
#: ../../c-api/memory.rst:287
msgid ""
"Same as :c:func:`PyMem_Realloc`, but the memory block is resized to ``(n * "
"sizeof(TYPE))`` bytes. Returns a pointer cast to ``TYPE*``. On return, *p* "
"will be a pointer to the new memory area, or ``NULL`` in the event of "
"failure."
msgstr ""
"与 :c:func:`PyMem_Realloc` 类似,但内存块的大小被调整为 ``(n * sizeof(TYPE))`` 个字节。返回一个转换为 "
"``TYPE*`` 的指针。在返回时,*p* 将是一个指向新内存区域的指针,或者如果执行失败则为 ``NULL``。"
#: ../../c-api/memory.rst:292
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 "这是一个 C 预处理宏, *p* 总是被重新赋值。请保存 *p* 的原始值,以避免在处理错误时丢失内存。"
#: ../../c-api/memory.rst:298
msgid "Same as :c:func:`PyMem_Free`."
msgstr "与 :c:func:`PyMem_Free` 相同"
#: ../../c-api/memory.rst:302
msgid "Deprecated aliases"
msgstr "一些已被弃用的别名"
#: ../../c-api/memory.rst:304
msgid ""
"These are :term:`soft deprecated` aliases to existing functions and macros. "
"They exist solely for backwards compatibility."
msgstr "这些是现有函数和宏的已处于 :term:`soft deprecated` 状态的别名。它们的存在只是为了向下兼容。"
#: ../../c-api/memory.rst:311
msgid "Deprecated alias"
msgstr "已弃用的别名"
#: ../../c-api/memory.rst:312
msgid "Corresponding function or macro"
msgstr "对应的函数或宏"
#: ../../c-api/memory.rst:314
msgid ":c:func:`PyMem_Malloc`"
msgstr ":c:func:`PyMem_Malloc`"
#: ../../c-api/memory.rst:316
msgid ":c:macro:`PyMem_New`"
msgstr ":c:macro:`PyMem_New`"
#: ../../c-api/memory.rst:318 ../../c-api/memory.rst:507
msgid ":c:func:`PyMem_Realloc`"
msgstr ":c:func:`PyMem_Realloc`"
#: ../../c-api/memory.rst:320
msgid ":c:macro:`PyMem_Resize`"
msgstr ":c:macro:`PyMem_Resize`"
#: ../../c-api/memory.rst:322 ../../c-api/memory.rst:324
#: ../../c-api/memory.rst:509
msgid ":c:func:`PyMem_Free`"
msgstr ":c:func:`PyMem_Free`"
#: ../../c-api/memory.rst:328
msgid ""
"The macros are now aliases of the corresponding functions and macros. "
"Previously, their behavior was the same, but their use did not necessarily "
"preserve binary compatibility across Python versions."
msgstr "这些宏现在是对应的函数和宏的别名。在之前版本中,它们的行为是相同的,但它们的使用不一定能跨 Python 版本保持二进制兼容。"
#: ../../c-api/memory.rst:338
msgid "Object allocators"
msgstr "对象分配器"
#: ../../c-api/memory.rst:345
msgid ""
"There is no guarantee that the memory returned by these allocators can be "
"successfully cast to a Python object when intercepting the allocating "
"functions in this domain by the methods described in the :ref:`Customize "
"Memory Allocators <customize-memory-allocators>` section."
msgstr ""
"当通过 :ref:`自定义内存分配器 <customize-memory-allocators>` "
"部分描述的方法拦截该域中的分配函数时,无法保证这些分配器返回的内存可以被成功地转换成 Python 对象。"
#: ../../c-api/memory.rst:350
msgid ""
"The :ref:`default object allocator <default-memory-allocators>` uses the "
":ref:`pymalloc memory allocator <pymalloc>`. In the :term:`free-threaded "
"<free threading>` build, the default is the :ref:`mimalloc memory allocator "
"<mimalloc>` instead."
msgstr ""
":ref:`默认对象分配器 <default-memory-allocators>` 使用 :ref:`pymalloc 内存分配器 "
"<pymalloc>`。 在 :term:`自由线程 <free threading>` 构建上,默认改用 :ref:`mimalloc 内存分配器 "
"<mimalloc>`。"
#: ../../c-api/memory.rst:364
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 ""
"请求零字节可能返回一个独特的非 ``NULL`` 指针,就像调用了 ``PyObject_Malloc(1)`` 一样。但是内存不会以任何方式被初始化。"
#: ../../c-api/memory.rst:375
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 "请求零字节可能返回一个独特的非 ``NULL`` 指针,就像调用了 ``PyObject_Calloc(1, 1)`` 一样。"
#: ../../c-api/memory.rst:387
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 ""
"如果 *p* 是 ``NULL``,则相当于调用 ``PyObject_Malloc(n)``;如果 *n* 等于 "
"0,则内存块大小会被调整,但不会被释放,返回非 ``NULL`` 指针。"
#: ../../c-api/memory.rst:391
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 ""
"除非 *p* 是 ``NULL``,否则它必须是之前调用 "
":c:func:`PyObject_Malloc`、:c:func:`PyObject_Realloc` 或 "
":c:func:`PyObject_Calloc` 所返回的。"
#: ../../c-api/memory.rst:394
msgid ""
"If the request fails, :c:func:`PyObject_Realloc` returns ``NULL`` and *p* "
"remains a valid pointer to the previous memory area."
msgstr "如果请求失败,:c:func:`PyObject_Realloc` 返回 ``NULL``,*p* 仍然是指向先前内存区域的有效指针。"
#: ../../c-api/memory.rst:400
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 ""
"释放 *p* 指向的内存块。*p* 必须是之前调用 "
":c:func:`PyObject_Malloc`、:c:func:`PyObject_Realloc` 或 "
":c:func:`PyObject_Calloc` 所返回的指针。否则,或在 ``PyObject_Free(p)`` "
"之前已经调用过的情况下,未定义行为会发生。"
#: ../../c-api/memory.rst:407
msgid ""
"Do not call this directly to free an object's memory; call the type's "
":c:member:`~PyTypeObject.tp_free` slot instead."
msgstr "请不要直接调用此函数来释放对象的内存;而应调用类型的 :c:member:`~PyTypeObject.tp_free` 槽位。"
#: ../../c-api/memory.rst:410
msgid ""
"Do not use this for memory allocated by :c:macro:`PyObject_GC_New` or "
":c:macro:`PyObject_GC_NewVar`; use :c:func:`PyObject_GC_Del` instead."
msgstr ""
"请不要为 :c:macro:`PyObject_GC_New` 或 :c:macro:`PyObject_GC_NewVar` "
"所分配的内存使用此宏;而应改用 :c:func:`PyObject_GC_Del`。"
#: ../../c-api/memory.rst:415
msgid ""
":c:func:`PyObject_GC_Del` is the equivalent of this function for memory "
"allocated by types that support garbage collection."
msgstr ":c:func:`PyObject_GC_Del` 是该函数针对由支持垃圾回收的类型分配的内存的等价物。"
#: ../../c-api/memory.rst:417 ../../c-api/memory.rst:515
msgid ":c:func:`PyObject_Malloc`"
msgstr ":c:func:`PyObject_Malloc`"
#: ../../c-api/memory.rst:418 ../../c-api/memory.rst:516
msgid ":c:func:`PyObject_Realloc`"
msgstr ":c:func:`PyObject_Realloc`"
#: ../../c-api/memory.rst:419 ../../c-api/memory.rst:517
msgid ":c:func:`PyObject_Calloc`"
msgstr ":c:func:`PyObject_Calloc`"
#: ../../c-api/memory.rst:420
msgid ":c:macro:`PyObject_New`"
msgstr ":c:macro:`PyObject_New`"
#: ../../c-api/memory.rst:421
msgid ":c:macro:`PyObject_NewVar`"
msgstr ":c:macro:`PyObject_NewVar`"
#: ../../c-api/memory.rst:422
msgid ":c:func:`PyType_GenericAlloc`"
msgstr ":c:func:`PyType_GenericAlloc`"
#: ../../c-api/memory.rst:423
msgid ":c:member:`~PyTypeObject.tp_free`"
msgstr ":c:member:`~PyTypeObject.tp_free`"
#: ../../c-api/memory.rst:429
msgid "Default Memory Allocators"
msgstr "默认内存分配器"
#: ../../c-api/memory.rst:431
msgid "Default memory allocators:"
msgstr "默认内存分配器:"
#: ../../c-api/memory.rst:434
msgid "Configuration"
msgstr "配置"
#: ../../c-api/memory.rst:434
msgid "Name"
msgstr "名称"
#: ../../c-api/memory.rst:434
msgid "PyMem_RawMalloc"
msgstr "PyMem_RawMalloc"
#: ../../c-api/memory.rst:434
msgid "PyMem_Malloc"
msgstr "PyMem_Malloc"
#: ../../c-api/memory.rst:434
msgid "PyObject_Malloc"
msgstr "PyObject_Malloc"
#: ../../c-api/memory.rst:436
msgid "Release build"
msgstr "发布版本"
#: ../../c-api/memory.rst:436
msgid "``\"pymalloc\"``"
msgstr "``\"pymalloc\"``"
#: ../../c-api/memory.rst:436 ../../c-api/memory.rst:438
msgid "``malloc``"
msgstr "``malloc``"
#: ../../c-api/memory.rst:436
msgid "``pymalloc``"
msgstr "``pymalloc``"
#: ../../c-api/memory.rst:437
msgid "Debug build"
msgstr "调试构建"
#: ../../c-api/memory.rst:437
msgid "``\"pymalloc_debug\"``"
msgstr "``\"pymalloc_debug\"``"
#: ../../c-api/memory.rst:437 ../../c-api/memory.rst:439
msgid "``malloc`` + debug"
msgstr "``malloc`` + debug"
#: ../../c-api/memory.rst:437
msgid "``pymalloc`` + debug"
msgstr "``pymalloc`` + debug"
#: ../../c-api/memory.rst:438
msgid "Release build, without pymalloc"
msgstr "没有 pymalloc 的发布版本"
#: ../../c-api/memory.rst:438
msgid "``\"malloc\"``"
msgstr "``\"malloc\"``"
#: ../../c-api/memory.rst:439
msgid "Debug build, without pymalloc"
msgstr "没有 pymalloc 的调试构建"
#: ../../c-api/memory.rst:439
msgid "``\"malloc_debug\"``"
msgstr "``\"malloc_debug\"``"
#: ../../c-api/memory.rst:440
msgid "Free-threaded build"
msgstr "自由线程构建版"
#: ../../c-api/memory.rst:440
msgid "``\"mimalloc\"``"
msgstr "``\"mimalloc\"``"
#: ../../c-api/memory.rst:440
msgid "``mimalloc``"
msgstr "``mimalloc``"
#: ../../c-api/memory.rst:441
msgid "Free-threaded debug build"
msgstr "自由线程调试构建版"
#: ../../c-api/memory.rst:441
msgid "``\"mimalloc_debug\"``"
msgstr "``\"mimalloc_debug\"``"
#: ../../c-api/memory.rst:441
msgid "``mimalloc`` + debug"
msgstr "``mimalloc`` + debug"
#: ../../c-api/memory.rst:444
msgid "Legend:"
msgstr "说明:"
#: ../../c-api/memory.rst:446
msgid "Name: value for :envvar:`PYTHONMALLOC` environment variable."
msgstr "名称::envvar:`PYTHONMALLOC` 环境变量的值。"
#: ../../c-api/memory.rst:447
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 ""
"``malloc``: 来自 C 标准库的系统分配器,C "
"函数::c:func:`malloc`、:c:func:`calloc`、:c:func:`realloc` 和 :c:func:`free`。"
#: ../../c-api/memory.rst:449
msgid "``pymalloc``: :ref:`pymalloc memory allocator <pymalloc>`."
msgstr "``pymalloc``: :ref:`pymalloc 内存分配器 <pymalloc>`。"
#: ../../c-api/memory.rst:450
msgid "``mimalloc``: :ref:`mimalloc memory allocator <mimalloc>`."
msgstr "``mimalloc``: :ref:`mimalloc 内存分配器 <mimalloc>`。"
#: ../../c-api/memory.rst:451
msgid ""
"\"+ debug\": with :ref:`debug hooks on the Python memory allocators <pymem-"
"debug-hooks>`."
msgstr "\"+ debug\": 附带 :ref:`Python 内存分配器的调试钩子 <pymem-debug-hooks>`."
#: ../../c-api/memory.rst:453
msgid "\"Debug build\": :ref:`Python build in debug mode <debug-build>`."
msgstr "“调试构建”::ref:`调试模式下的 Python 构建 <debug-build>`。"
#: ../../c-api/memory.rst:458
msgid "Customize Memory Allocators"
msgstr "自定义内存分配器"
#: ../../c-api/memory.rst:464
msgid ""
"Structure used to describe a memory block allocator. The structure has the "
"following fields:"
msgstr "用于描述内存块分配器的结构体。该结构体具有下列字段:"
#: ../../c-api/memory.rst:468 ../../c-api/memory.rst:723
msgid "Field"
msgstr "域"
#: ../../c-api/memory.rst:468 ../../c-api/memory.rst:723
msgid "Meaning"
msgstr "含义"
#: ../../c-api/memory.rst:470 ../../c-api/memory.rst:725
msgid "``void *ctx``"
msgstr "``void *ctx``"
#: ../../c-api/memory.rst:470 ../../c-api/memory.rst:725
msgid "user context passed as first argument"
msgstr "作为第一个参数传入的用户上下文"
#: ../../c-api/memory.rst:472
msgid "``void* malloc(void *ctx, size_t size)``"
msgstr "``void* malloc(void *ctx, size_t size)``"
#: ../../c-api/memory.rst:472
msgid "allocate a memory block"
msgstr "分配一个内存块"
#: ../../c-api/memory.rst:474
msgid "``void* calloc(void *ctx, size_t nelem, size_t elsize)``"
msgstr "``void* calloc(void *ctx, size_t nelem, size_t elsize)``"
#: ../../c-api/memory.rst:474
msgid "allocate a memory block initialized with zeros"
msgstr "分配一个初始化为 0 的内存块"
#: ../../c-api/memory.rst:477
msgid "``void* realloc(void *ctx, void *ptr, size_t new_size)``"
msgstr "``void* realloc(void *ctx, void *ptr, size_t new_size)``"
#: ../../c-api/memory.rst:477
msgid "allocate or resize a memory block"
msgstr "分配一个内存块或调整其大小"
#: ../../c-api/memory.rst:479
msgid "``void free(void *ctx, void *ptr)``"
msgstr "``void free(void *ctx, void *ptr)``"
#: ../../c-api/memory.rst:479
msgid "free a memory block"
msgstr "释放一个内存块"
#: ../../c-api/memory.rst:482
msgid ""
"The :c:type:`!PyMemAllocator` structure was renamed to "
":c:type:`PyMemAllocatorEx` and a new ``calloc`` field was added."
msgstr ""
":c:type:`!PyMemAllocator` 结构被重命名为 :c:type:`PyMemAllocatorEx` 并新增了一个 "
"``calloc`` 字段。"
#: ../../c-api/memory.rst:489
msgid "Enum used to identify an allocator domain. Domains:"
msgstr "用来识别分配器域的枚举类。域有:"
#: ../../c-api/memory.rst:495 ../../c-api/memory.rst:504
#: ../../c-api/memory.rst:513
msgid "Functions:"
msgstr "函数"
#: ../../c-api/memory.rst:497
msgid ":c:func:`PyMem_RawMalloc`"
msgstr ":c:func:`PyMem_RawMalloc`"
#: ../../c-api/memory.rst:498
msgid ":c:func:`PyMem_RawRealloc`"
msgstr ":c:func:`PyMem_RawRealloc`"
#: ../../c-api/memory.rst:499
msgid ":c:func:`PyMem_RawCalloc`"
msgstr ":c:func:`PyMem_RawCalloc`"
#: ../../c-api/memory.rst:500
msgid ":c:func:`PyMem_RawFree`"
msgstr ":c:func:`PyMem_RawFree`"
#: ../../c-api/memory.rst:506
msgid ":c:func:`PyMem_Malloc`,"
msgstr ":c:func:`PyMem_Malloc`,"
#: ../../c-api/memory.rst:508
msgid ":c:func:`PyMem_Calloc`"
msgstr ":c:func:`PyMem_Calloc`"
#: ../../c-api/memory.rst:518
msgid ":c:func:`PyObject_Free`"
msgstr ":c:func:`PyObject_Free`"
#: ../../c-api/memory.rst:522
msgid "Get the memory block allocator of the specified domain."
msgstr "获取指定域的内存块分配器。"
#: ../../c-api/memory.rst:527
msgid "Set the memory block allocator of the specified domain."
msgstr "设置指定域的内存块分配器。"
#: ../../c-api/memory.rst:529
msgid ""
"The new allocator must return a distinct non-``NULL`` pointer when "
"requesting zero bytes."
msgstr "当请求零字节时,新的分配器必须返回一个独特的非 ``NULL`` 指针。"
#: ../../c-api/memory.rst:532
msgid ""
"For the :c:macro:`PYMEM_DOMAIN_RAW` domain, the allocator must be thread-"
"safe: a :term:`thread state` is not :term:`attached <attached thread state>`"
" when the allocator is called."
msgstr ""
"对于 :c:macro:`PYMEM_DOMAIN_RAW` 域,分配器必须是线程安全的:当分配器被调用时 :term:`thread state` "
"是没有 :term:`附加的 <attached thread state>`。"
#: ../../c-api/memory.rst:536
msgid ""
"For the remaining domains, the allocator must also be thread-safe: the "
"allocator may be called in different interpreters that do not share a "
":term:`GIL`."
msgstr "对于其余的域,分配器也必须是线程安全的:分配器可以在不共享 :term:`GIL` 的不同解释器中被调用。"
#: ../../c-api/memory.rst:540
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 ""
"如果新的分配器不是钩子(不调用之前的分配器),必须调用 :c:func:`PyMem_SetupDebugHooks` "
"函数在新分配器上重新安装调试钩子。"
#: ../../c-api/memory.rst:544
msgid ""
"See also :c:member:`PyPreConfig.allocator` and :ref:`Preinitialize Python "
"with PyPreConfig <c-preinit>`."
msgstr ""
"另请参阅 :c:member:`PyPreConfig.allocator` 和 :ref:`Preinitialize Python with "
"PyPreConfig <c-preinit>` 一节。"
#: ../../c-api/memory.rst:549
msgid ":c:func:`PyMem_SetAllocator` does have the following contract:"
msgstr ":c:func:`PyMem_SetAllocator` 确实具有以下合约:"
#: ../../c-api/memory.rst:551
msgid ""
"It can be called after :c:func:`Py_PreInitialize` and before "
":c:func:`Py_InitializeFromConfig` to install a custom memory allocator. "
"There are no restrictions over the installed allocator other than the ones "
"imposed by the domain (for instance, the Raw Domain allows the allocator to "
"be called without an :term:`attached thread state`). See :ref:`the section "
"on allocator domains <allocator-domains>` for more information."
msgstr ""
"可以在 :c:func:`Py_PreInitialize` 之后和 :c:func:`Py_InitializeFromConfig` "
"之前调用它来安装自定义的内存分配器。对于所安装的分配器除了域的规定以外没有任何其他限制(例如 Raw Domain 允许分配器在没有 "
":term:`attached thread state` 的情况下被调用)。请参阅 :ref:`有关分配器域的章节 <allocator-"
"domains>` 来了解详情。"
#: ../../c-api/memory.rst:559
msgid ""
"If called after Python has finish initializing (after "
":c:func:`Py_InitializeFromConfig` has been called) the allocator **must** "
"wrap the existing allocator. Substituting the current allocator for some "
"other arbitrary one is **not supported**."
msgstr ""
"如果在 Python 已完成初始化之后(即 :c:func:`Py_InitializeFromConfig` "
"被调用之后)被调用则自定义分配器**必须**包装现有的分配器。将现有分配器替换为任意的其他分配器是 **不受支持的**。"
#: ../../c-api/memory.rst:564
msgid "All allocators must be thread-safe."
msgstr "所有分配器都必须是线程安全的。"
#: ../../c-api/memory.rst:570
msgid ""
"Setup :ref:`debug hooks in the Python memory allocators <pymem-debug-hooks>`"
" to detect memory errors."
msgstr "设置 :ref:`Python 内存分配器的调试钩子 <pymem-debug-hooks>` 以检测内存错误。"
#: ../../c-api/memory.rst:577
msgid "Debug hooks on the Python memory allocators"
msgstr "Python 内存分配器的调试钩子"
#: ../../c-api/memory.rst:579
msgid ""
"When :ref:`Python is built in debug mode <debug-build>`, the "
":c:func:`PyMem_SetupDebugHooks` function is called at the :ref:`Python "
"preinitialization <c-preinit>` to setup debug hooks on Python memory "
"allocators to detect memory errors."
msgstr ""
"当 :ref:`Python 在调试模式下构建 <debug-build>`,:c:func:`PyMem_SetupDebugHooks` 函数在 "
":ref:`Python 预初始化 <c-preinit>` 时被调用,以在 Python 内存分配器上设置调试钩子以检测内存错误。"
#: ../../c-api/memory.rst:584
msgid ""
"The :envvar:`PYTHONMALLOC` environment variable can be used to install debug"
" hooks on a Python compiled in release mode (ex: ``PYTHONMALLOC=debug``)."
msgstr ""
":envvar:`PYTHONMALLOC` 环境变量可被用于在以发行模式下编译的 Python 上安装调试钩子 (例如: "
"``PYTHONMALLOC=debug``)。"
#: ../../c-api/memory.rst:587
msgid ""
"The :c:func:`PyMem_SetupDebugHooks` function can be used to set debug hooks "
"after calling :c:func:`PyMem_SetAllocator`."
msgstr ""
":c:func:`PyMem_SetupDebugHooks` 函数可被用于在调用了 :c:func:`PyMem_SetAllocator` "
"之后设置调试钩子。"
#: ../../c-api/memory.rst:590
msgid ""
"These debug hooks fill dynamically allocated memory blocks with special, "
"recognizable bit patterns. Newly allocated memory is filled with the byte "
"``0xCD`` (``PYMEM_CLEANBYTE``), freed memory is filled with the byte "
"``0xDD`` (``PYMEM_DEADBYTE``). Memory blocks are surrounded by \"forbidden "
"bytes\" filled with the byte ``0xFD`` (``PYMEM_FORBIDDENBYTE``). Strings of "
"these bytes are unlikely to be valid addresses, floats, or ASCII strings."
msgstr ""
"这些调试钩子用特殊的、可辨认的位模式填充动态分配的内存块。新分配的内存用字节 ``0xCD`` (``PYMEM_CLEANBYTE``) "
"填充,释放的内存用字节 ``0xDD`` (``PYMEM_DEADBYTE``) 填充。内存块被填充了字节 ``0xFD`` "
"(``PYMEM_FORBIDDENBYTE``) 的“禁止字节”包围。这些字节串不太可能是合法的地址、浮点数或 ASCII 字符串。"
#: ../../c-api/memory.rst:597