-
-
Notifications
You must be signed in to change notification settings - Fork 37
Expand file tree
/
Copy pathmemory.po
More file actions
1349 lines (1142 loc) · 51.7 KB
/
memory.po
File metadata and controls
1349 lines (1142 loc) · 51.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:
# mollinaca, 2021
# yaakiyu, 2022
# Arihiro TAKASE, 2023
# tomo, 2025
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.14\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-05-23 14:20+0000\n"
"PO-Revision-Date: 2021-06-28 00:49+0000\n"
"Last-Translator: tomo, 2025\n"
"Language-Team: Japanese (https://app.transifex.com/python-doc/teams/5390/"
"ja/)\n"
"Language: ja\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
#: ../../c-api/memory.rst:8
msgid "Memory Management"
msgstr "メモリ管理"
#: ../../c-api/memory.rst:17
msgid "Overview"
msgstr "概要"
#: ../../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 ""
"Python におけるメモリ管理には、全ての Python オブジェクトとデータ構造が入った"
"プライベートヒープ (private heap) が必須です。プライベートヒープの管理は、内"
"部的には *Python メモリマネージャ (Python memory manager)* が確実に行います。"
"Python メモリマネージャには、共有 (sharing)、セグメント分割 (segmentation)、"
"事前割り当て (preallocation)、キャッシュ化 (caching) といった、様々な動的記憶"
"管理の側面を扱うために、個別のコンポーネントがあります。"
#: ../../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 ""
"最低水準層では、素のメモリ操作関数 (raw memory allocator) がオペレーティング"
"システムのメモリ管理機構とやりとりして、プライベートヒープ内にPython 関連の全"
"てのデータを記憶するのに十分な空きがあるかどうか確認します。素のメモリ操作関"
"数の上には、いくつかのオブジェクト固有のメモリ操作関数があります。これらは同"
"じヒープを操作し、各オブジェクト型固有の事情に合ったメモリ管理ポリシを実装し"
"ています。例えば、整数オブジェクトは文字列やタプル、辞書とは違ったやり方で"
"ヒープ内で管理されます。というのも、整数には値を記憶する上で特別な要件があ"
"り、速度/容量のトレードオフが存在するからです。このように、Python メモリマネ"
"ジャは作業のいくつかをオブジェクト固有のメモリ操作関数に委譲しますが、これら"
"の関数がプライベートヒープからはみ出してメモリ管理を行わないようにしていま"
"す。"
#: ../../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 ""
"重要なのは、たとえユーザがいつもヒープ内のメモリブロックを指すようなオブジェ"
"クトポインタを操作しているとしても、Python 用ヒープの管理はインタプリタ自体が"
"行うもので、ユーザがそれを制御する余地はないと理解することです。Python オブ"
"ジェクトや内部使用されるバッファを入れるためのヒープ空間のメモリ確保は、必要"
"に応じて、Python メモリマネージャがこのドキュメント内で列挙しているPython/C "
"API 関数群を介して行います。"
#: ../../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 ""
"メモリ管理の崩壊を避けるため、拡張モジュールの作者は決して Python オブジェク"
"トを C ライブラリが公開している関数: :c:func:`malloc` 、 :c:func:"
"`calloc` 、 :c:func:`realloc` および :c:func:`free` で操作しようとしてはなり"
"ません。こうした関数を使うと、C のメモリ操作関数と Python メモリマネージャと"
"の間で関数呼び出しが交錯します。 C のメモリ操作関数とPython メモリマネージャ"
"は異なるアルゴリズムで実装されていて、異なるヒープを操作するため、呼び出しの"
"交錯は致命的な結果を招きます。とはいえ、個別の目的のためなら、 C ライブラリの"
"メモリ操作関数を使って安全にメモリを確保したり解放したりできます。例えば、以"
"下がそのような例です::"
#: ../../c-api/memory.rst:58
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 ""
#: ../../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 bytes object returned as a result."
msgstr ""
"この例では、I/O バッファに対するメモリ要求は C ライブラリのメモリ操作関数を"
"使っています。Python メモリマネージャーは戻り値として返される bytes オブジェ"
"クトを確保する時にだけ必要です。"
#: ../../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 ""
"とはいえ、ほとんどの状況では、メモリの操作は Python ヒープに固定して行うよう"
"勧めます。なぜなら、Python ヒープは Python メモリマネジャの管理下にあるからで"
"す。例えば、インタプリタを C で書かれた新たなオブジェクト型で拡張する際には、"
"ヒープでのメモリ管理が必要です。Python ヒープを使った方がよいもう一つの理由と"
"して、拡張モジュールが必要としているメモリについて Python メモリマネージャに "
"*情報を提供* してほしいということがあります。たとえ必要なメモリが内部的かつ非"
"常に特化した用途に対して排他的に用いられるものだとしても、全てのメモリ操作要"
"求を Python メモリマネージャに委譲すれば、インタプリタはより正確なメモリフッ"
"トプリントの全体像を把握できます。その結果、特定の状況では、Python メモリマ"
"ネージャがガベージコレクションやメモリのコンパクト化、その他何らかの予防措置"
"といった、適切な動作をトリガできることがあります。上の例で示したように C ライ"
"ブラリのメモリ操作関数を使うと、I/O バッファ用に確保したメモリは Python メモ"
"リマネージャの管理から完全に外れることに注意してください。"
#: ../../c-api/memory.rst:88
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: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 ""
"環境変数 :envvar:`PYTHONMALLOCSTATS` を使用して、新たなオブジェクトアリーナが"
"生成される時と、シャットダウン時に :ref:`pymalloc メモリアロケータ "
"<pymalloc>` の統計情報を表示できます。"
#: ../../c-api/memory.rst:96
msgid "Allocator Domains"
msgstr ""
#: ../../c-api/memory.rst:100
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:`here <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-api/memory.rst:109
msgid "The three allocation domains are:"
msgstr ""
#: ../../c-api/memory.rst:111
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 ""
#: ../../c-api/memory.rst:116
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 ""
#: ../../c-api/memory.rst:121
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 ""
#: ../../c-api/memory.rst:126
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 ""
#: ../../c-api/memory.rst:130
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 ""
#: ../../c-api/memory.rst:133
msgid "See :ref:`Memory Allocation APIs <free-threaded-memory-allocation>`."
msgstr ""
#: ../../c-api/memory.rst:139
msgid "Raw Memory Interface"
msgstr "生メモリインターフェース"
#: ../../c-api/memory.rst:141
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 ""
#: ../../c-api/memory.rst:145
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 ""
#: ../../c-api/memory.rst:154 ../../c-api/memory.rst:224
#: ../../c-api/memory.rst:333
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:157
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 ""
"0バイトを要求すると、 ``PyMem_RawMalloc(1)`` が呼ばれたときと同じように、可能"
"なら ``NULL`` でないユニークなポインタを返します。確保されたメモリーにはいか"
"なる初期化も行われません。"
#: ../../c-api/memory.rst:164 ../../c-api/memory.rst:234
#: ../../c-api/memory.rst:343
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 ""
"各要素が *elsize* バイトの要素 *nelem* 個分のメモリーを確保し、そのメモリーを"
"指す :c:expr:`void*` 型のポインタを返します。アロケートに失敗した場合は "
"``NULL`` を返します。確保されたメモリー領域はゼロで初期化されます。"
#: ../../c-api/memory.rst:168
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 ""
"要素数か要素のサイズが0バイトの要求に対しては、可能なら ``PyMem_RawCalloc(1, "
"1)`` が呼ばれたのと同じように、ユニークな ``NULL`` でないポインタを返します。"
#: ../../c-api/memory.rst:177 ../../c-api/memory.rst:247
#: ../../c-api/memory.rst:356
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:180
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* がゼロに等しい場合、メモリブロックはリサイズされますが解放されませ"
"ん。返されたポインタは非 ``NULL`` です。"
#: ../../c-api/memory.rst:184
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`` でない限り、*p* はそれより前の :c:func:`PyMem_RawMalloc`, :c:"
"func:`PyMem_RawRealloc`, :c:func:`PyMem_RawCalloc` の呼び出しにより返されなけ"
"ればなりません。"
#: ../../c-api/memory.rst:188
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:194
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:199 ../../c-api/memory.rst:268
#: ../../c-api/memory.rst:377
msgid "If *p* is ``NULL``, no operation is performed."
msgstr "*p* が ``NULL`` の場合何もしません。"
#: ../../c-api/memory.rst:205
msgid "Memory Interface"
msgstr "メモリインターフェース"
#: ../../c-api/memory.rst:207 ../../c-api/memory.rst:314
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 ""
"以下の関数群が利用して Python ヒープに対してメモリを確保したり解放したり出来"
"ます。これらの関数は ANSI C 標準に従ってモデル化されていますが、0 バイトを要"
"求した際の動作についても定義しています:"
#: ../../c-api/memory.rst:211
msgid ""
"The :ref:`default memory allocator <default-memory-allocators>` uses the :"
"ref:`pymalloc memory allocator <pymalloc>`."
msgstr ""
#: ../../c-api/memory.rst:216 ../../c-api/memory.rst:329
msgid ""
"There must be an :term:`attached thread state` when using these functions."
msgstr ""
#: ../../c-api/memory.rst:220
msgid ""
"The default allocator is now pymalloc instead of system :c:func:`malloc`."
msgstr ""
"デフォルトのアロケータがシステムの :c:func:`malloc` から pymalloc になりまし"
"た。"
#: ../../c-api/memory.rst:227
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 ""
"0バイトを要求すると、 ``PyMem_Malloc(1)`` が呼ばれたときと同じように、可能な"
"ら ``NULL`` でないユニークなポインタを返します。\n"
"確保されたメモリーにはいかなる初期化も行われません。"
#: ../../c-api/memory.rst:238
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 ""
"要素数か要素のサイズが0バイトの要求に対しては、可能なら ``PyMem_Calloc(1, "
"1)`` が呼ばれたのと同じように、ユニークな ``NULL`` でないポインタを返します。"
#: ../../c-api/memory.rst:250
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* がゼロに等しい場合、メモリブロックはリサイズされますが解放されませ"
"ん。返されたポインタは非 ``NULL`` です。"
#: ../../c-api/memory.rst:254
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`` でない限り、*p* はそれより前の :c:func:`PyMem_Malloc`, :c:"
"func:`PyMem_Realloc` または :c:func:`PyMem_Calloc` の呼び出しにより返されなけ"
"ればなりません。"
#: ../../c-api/memory.rst:257
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:263
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:270
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:276
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-api/memory.rst:283
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-api/memory.rst:288
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:294
msgid "Same as :c:func:`PyMem_Free`."
msgstr ":c:func:`PyMem_Free` と同じです。"
#: ../../c-api/memory.rst:296
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 ""
"上記に加えて、C API 関数を介することなく Python メモリ操作関数を直接呼び出す"
"ための以下のマクロセットが提供されています。ただし、これらのマクロは Python "
"バージョン間でのバイナリ互換性を保てず、それゆえに拡張モジュールでは撤廃され"
"ているので注意してください。"
#: ../../c-api/memory.rst:301
msgid "``PyMem_MALLOC(size)``"
msgstr "``PyMem_MALLOC(size)``"
#: ../../c-api/memory.rst:302
msgid "``PyMem_NEW(type, size)``"
msgstr "``PyMem_NEW(type, size)``"
#: ../../c-api/memory.rst:303
msgid "``PyMem_REALLOC(ptr, size)``"
msgstr "``PyMem_REALLOC(ptr, size)``"
#: ../../c-api/memory.rst:304
msgid "``PyMem_RESIZE(ptr, type, size)``"
msgstr "``PyMem_RESIZE(ptr, type, size)``"
#: ../../c-api/memory.rst:305
msgid "``PyMem_FREE(ptr)``"
msgstr "``PyMem_FREE(ptr)``"
#: ../../c-api/memory.rst:306
msgid "``PyMem_DEL(ptr)``"
msgstr "``PyMem_DEL(ptr)``"
#: ../../c-api/memory.rst:312
msgid "Object allocators"
msgstr "オブジェクトアロケータ"
#: ../../c-api/memory.rst:319
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 ""
#: ../../c-api/memory.rst:324
msgid ""
"The :ref:`default object allocator <default-memory-allocators>` uses the :"
"ref:`pymalloc memory allocator <pymalloc>`."
msgstr ""
#: ../../c-api/memory.rst:336
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 ""
"0バイトを要求すると、 ``PyObject_Malloc(1)`` が呼ばれたときと同じように、可能"
"なら ``NULL`` でないユニークなポインタを返します。\n"
"確保されたメモリーにはいかなる初期化も行われません。"
#: ../../c-api/memory.rst:347
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 ""
"要素数か要素のサイズが0バイトの要求に対しては、可能なら ``PyObject_Calloc(1, "
"1)`` が呼ばれたのと同じように、ユニークな ``NULL`` でないポインタを返します。"
#: ../../c-api/memory.rst:359
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* がゼロに等しい場合、メモリブロックはリサイズされますが解放されませ"
"ん。返されたポインタは非 ``NULL`` です。"
#: ../../c-api/memory.rst:363
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`` でない限り、*p* はそれより前の :c:func:`PyObject_Malloc`, :c:"
"func:`PyObject_Realloc` または :c:func:`PyObject_Calloc` の呼び出しにより返さ"
"れなければなりません。"
#: ../../c-api/memory.rst:366
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:372
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:379
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-api/memory.rst:382
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-api/memory.rst:387
msgid ""
":c:func:`PyObject_GC_Del` is the equivalent of this function for memory "
"allocated by types that support garbage collection."
msgstr ""
#: ../../c-api/memory.rst:389 ../../c-api/memory.rst:486
msgid ":c:func:`PyObject_Malloc`"
msgstr ":c:func:`PyObject_Malloc`"
#: ../../c-api/memory.rst:390 ../../c-api/memory.rst:487
msgid ":c:func:`PyObject_Realloc`"
msgstr ":c:func:`PyObject_Realloc`"
#: ../../c-api/memory.rst:391 ../../c-api/memory.rst:488
msgid ":c:func:`PyObject_Calloc`"
msgstr ":c:func:`PyObject_Calloc`"
#: ../../c-api/memory.rst:392
msgid ":c:macro:`PyObject_New`"
msgstr ""
#: ../../c-api/memory.rst:393
msgid ":c:macro:`PyObject_NewVar`"
msgstr ""
#: ../../c-api/memory.rst:394
msgid ":c:func:`PyType_GenericAlloc`"
msgstr ""
#: ../../c-api/memory.rst:395
msgid ":c:member:`~PyTypeObject.tp_free`"
msgstr ":c:member:`~PyTypeObject.tp_free`"
#: ../../c-api/memory.rst:401
msgid "Default Memory Allocators"
msgstr ""
#: ../../c-api/memory.rst:403
msgid "Default memory allocators:"
msgstr ""
#: ../../c-api/memory.rst:406
msgid "Configuration"
msgstr "Configuration"
#: ../../c-api/memory.rst:406
msgid "Name"
msgstr "名前"
#: ../../c-api/memory.rst:406
msgid "PyMem_RawMalloc"
msgstr "PyMem_RawMalloc"
#: ../../c-api/memory.rst:406
msgid "PyMem_Malloc"
msgstr "PyMem_Malloc"
#: ../../c-api/memory.rst:406
msgid "PyObject_Malloc"
msgstr "PyObject_Malloc"
#: ../../c-api/memory.rst:408
msgid "Release build"
msgstr "リリースビルド"
#: ../../c-api/memory.rst:408
msgid "``\"pymalloc\"``"
msgstr "``\"pymalloc\"``"
#: ../../c-api/memory.rst:408 ../../c-api/memory.rst:410
msgid "``malloc``"
msgstr "``malloc``"
#: ../../c-api/memory.rst:408
msgid "``pymalloc``"
msgstr "``pymalloc``"
#: ../../c-api/memory.rst:409
msgid "Debug build"
msgstr "デバッグビルド"
#: ../../c-api/memory.rst:409
msgid "``\"pymalloc_debug\"``"
msgstr "``\"pymalloc_debug\"``"
#: ../../c-api/memory.rst:409 ../../c-api/memory.rst:411
msgid "``malloc`` + debug"
msgstr "``malloc`` + debug"
#: ../../c-api/memory.rst:409
msgid "``pymalloc`` + debug"
msgstr "``pymalloc`` + debug"
#: ../../c-api/memory.rst:410
msgid "Release build, without pymalloc"
msgstr "pymalloc 無しのリリースビルド"
#: ../../c-api/memory.rst:410
msgid "``\"malloc\"``"
msgstr "``\"malloc\"``"
#: ../../c-api/memory.rst:411
msgid "Debug build, without pymalloc"
msgstr "pymalloc 無しのデバッグビルド"
#: ../../c-api/memory.rst:411
msgid "``\"malloc_debug\"``"
msgstr "``\"malloc_debug\"``"
#: ../../c-api/memory.rst:414
msgid "Legend:"
msgstr "説明:"
#: ../../c-api/memory.rst:416
msgid "Name: value for :envvar:`PYTHONMALLOC` environment variable."
msgstr ""
#: ../../c-api/memory.rst:417
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 ""
#: ../../c-api/memory.rst:419
msgid "``pymalloc``: :ref:`pymalloc memory allocator <pymalloc>`."
msgstr ""
#: ../../c-api/memory.rst:420
msgid ""
"``mimalloc``: :ref:`mimalloc memory allocator <mimalloc>`. The pymalloc "
"allocator will be used if mimalloc support isn't available."
msgstr ""
#: ../../c-api/memory.rst:422
msgid ""
"\"+ debug\": with :ref:`debug hooks on the Python memory allocators <pymem-"
"debug-hooks>`."
msgstr ""
#: ../../c-api/memory.rst:424
msgid "\"Debug build\": :ref:`Python build in debug mode <debug-build>`."
msgstr ""
#: ../../c-api/memory.rst:429
msgid "Customize Memory Allocators"
msgstr "メモリアロケータをカスタマイズする"
#: ../../c-api/memory.rst:435
msgid ""
"Structure used to describe a memory block allocator. The structure has the "
"following fields:"
msgstr ""
#: ../../c-api/memory.rst:439 ../../c-api/memory.rst:686
msgid "Field"
msgstr "フィールド"
#: ../../c-api/memory.rst:439 ../../c-api/memory.rst:686
msgid "Meaning"
msgstr "意味"
#: ../../c-api/memory.rst:441 ../../c-api/memory.rst:688
msgid "``void *ctx``"
msgstr "``void *ctx``"
#: ../../c-api/memory.rst:441 ../../c-api/memory.rst:688
msgid "user context passed as first argument"
msgstr "第一引数として渡されるユーザコンテキスト"
#: ../../c-api/memory.rst:443
msgid "``void* malloc(void *ctx, size_t size)``"
msgstr "``void* malloc(void *ctx, size_t size)``"
#: ../../c-api/memory.rst:443
msgid "allocate a memory block"
msgstr "メモリブロックを割り当てます"
#: ../../c-api/memory.rst:445
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:445
msgid "allocate a memory block initialized with zeros"
msgstr "0で初期化されたメモリブロックを割り当てます"
#: ../../c-api/memory.rst:448
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:448
msgid "allocate or resize a memory block"
msgstr "メモリブロックを割り当てるかリサイズします"
#: ../../c-api/memory.rst:450
msgid "``void free(void *ctx, void *ptr)``"
msgstr "``void free(void *ctx, void *ptr)``"
#: ../../c-api/memory.rst:450
msgid "free a memory block"
msgstr "メモリブロックを解放する"
#: ../../c-api/memory.rst:453
msgid ""
"The :c:type:`!PyMemAllocator` structure was renamed to :c:type:"
"`PyMemAllocatorEx` and a new ``calloc`` field was added."
msgstr ""
#: ../../c-api/memory.rst:460
msgid "Enum used to identify an allocator domain. Domains:"
msgstr "アロケータドメインを同定するための列挙型です。ドメインは:"
#: ../../c-api/memory.rst:466 ../../c-api/memory.rst:475
#: ../../c-api/memory.rst:484
msgid "Functions:"
msgstr "関数:"
#: ../../c-api/memory.rst:468
msgid ":c:func:`PyMem_RawMalloc`"
msgstr ":c:func:`PyMem_RawMalloc`"
#: ../../c-api/memory.rst:469
msgid ":c:func:`PyMem_RawRealloc`"
msgstr ":c:func:`PyMem_RawRealloc`"
#: ../../c-api/memory.rst:470
msgid ":c:func:`PyMem_RawCalloc`"
msgstr ":c:func:`PyMem_RawCalloc`"
#: ../../c-api/memory.rst:471
msgid ":c:func:`PyMem_RawFree`"
msgstr ":c:func:`PyMem_RawFree`"
#: ../../c-api/memory.rst:477
msgid ":c:func:`PyMem_Malloc`,"
msgstr ":c:func:`PyMem_Malloc`,"
#: ../../c-api/memory.rst:478
msgid ":c:func:`PyMem_Realloc`"
msgstr ":c:func:`PyMem_Realloc`"
#: ../../c-api/memory.rst:479
msgid ":c:func:`PyMem_Calloc`"
msgstr ":c:func:`PyMem_Calloc`"
#: ../../c-api/memory.rst:480
msgid ":c:func:`PyMem_Free`"
msgstr ":c:func:`PyMem_Free`"
#: ../../c-api/memory.rst:489
msgid ":c:func:`PyObject_Free`"
msgstr ":c:func:`PyObject_Free`"
#: ../../c-api/memory.rst:493
msgid "Get the memory block allocator of the specified domain."
msgstr "指定されたドメインのメモリブロックアロケータを取得します。"
#: ../../c-api/memory.rst:498
msgid "Set the memory block allocator of the specified domain."
msgstr "指定されたドメインのメモリブロックアロケータを設定します。"
#: ../../c-api/memory.rst:500
msgid ""
"The new allocator must return a distinct non-``NULL`` pointer when "
"requesting zero bytes."
msgstr ""
"新しいアロケータは、0バイトを要求されたときユニークな ``NULL`` でないポインタ"
"を返さなければなりません。"
#: ../../c-api/memory.rst:503
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-api/memory.rst:507
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 ""
#: ../../c-api/memory.rst:511
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 ""
"新しいアロケータがフックでない (1つ前のアロケータを呼び出さない) 場合、 :c:"
"func:`PyMem_SetupDebugHooks` 関数を呼び出して、新しいアロケータの上にデバッグ"
"フックを再度設置しなければなりません。"
#: ../../c-api/memory.rst:515
msgid ""
"See also :c:member:`PyPreConfig.allocator` and :ref:`Preinitialize Python "
"with PyPreConfig <c-preinit>`."
msgstr ""
#: ../../c-api/memory.rst:520
msgid ":c:func:`PyMem_SetAllocator` does have the following contract:"
msgstr ""
#: ../../c-api/memory.rst:522
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-api/memory.rst:530
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 ""
#: ../../c-api/memory.rst:535
msgid "All allocators must be thread-safe."
msgstr ""
#: ../../c-api/memory.rst:541
msgid ""
"Setup :ref:`debug hooks in the Python memory allocators <pymem-debug-hooks>` "
"to detect memory errors."
msgstr ""
#: ../../c-api/memory.rst:548
msgid "Debug hooks on the Python memory allocators"
msgstr ""
#: ../../c-api/memory.rst:550
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 ""
#: ../../c-api/memory.rst:555
msgid ""
"The :envvar:`PYTHONMALLOC` environment variable can be used to install debug "
"hooks on a Python compiled in release mode (ex: ``PYTHONMALLOC=debug``)."
msgstr ""
#: ../../c-api/memory.rst:558
msgid ""
"The :c:func:`PyMem_SetupDebugHooks` function can be used to set debug hooks "
"after calling :c:func:`PyMem_SetAllocator`."
msgstr ""
#: ../../c-api/memory.rst:561
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 ""
#: ../../c-api/memory.rst:568
msgid "Runtime checks:"
msgstr "実行時チェック:"
#: ../../c-api/memory.rst:570
msgid ""
"Detect API violations. For example, detect if :c:func:`PyObject_Free` is "
"called on a memory block allocated by :c:func:`PyMem_Malloc`."
msgstr ""
#: ../../c-api/memory.rst:572
msgid "Detect write before the start of the buffer (buffer underflow)."
msgstr ""
#: ../../c-api/memory.rst:573
msgid "Detect write after the end of the buffer (buffer overflow)."
msgstr ""
#: ../../c-api/memory.rst:574
msgid ""
"Check that there is an :term:`attached thread state` when allocator "
"functions of :c:macro:`PYMEM_DOMAIN_OBJ` (ex: :c:func:`PyObject_Malloc`) "
"and :c:macro:`PYMEM_DOMAIN_MEM` (ex: :c:func:`PyMem_Malloc`) domains are "
"called."
msgstr ""