-
-
Notifications
You must be signed in to change notification settings - Fork 37
Expand file tree
/
Copy pathintro.po
More file actions
1815 lines (1599 loc) · 78.1 KB
/
intro.po
File metadata and controls
1815 lines (1599 loc) · 78.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
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, 2025
# qqfunc, 2025
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.14\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-03-09 14:44+0000\n"
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
"Last-Translator: qqfunc, 2025\n"
"Language-Team: Japanese (https://app.transifex.com/python-doc/teams/5390/"
"ja/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: ja\n"
"Plural-Forms: nplurals=1; plural=0;\n"
#: ../../c-api/intro.rst:8
msgid "Introduction"
msgstr "はじめに"
#: ../../c-api/intro.rst:10
msgid ""
"The Application Programmer's Interface to Python gives C and C++ programmers "
"access to the Python interpreter at a variety of levels. The API is equally "
"usable from C++, but for brevity it is generally referred to as the Python/C "
"API. There are two fundamentally different reasons for using the Python/C "
"API. The first reason is to write *extension modules* for specific purposes; "
"these are C modules that extend the Python interpreter. This is probably "
"the most common use. The second reason is to use Python as a component in a "
"larger application; this technique is generally referred to as :dfn:"
"`embedding` Python in an application."
msgstr ""
"Python のアプリケーションプログラマ用インタフェース (Application "
"Programmer's Interface, API) は、 Python インタプリタに対する様々なレベルでの"
"アクセス手段を C や C++ のプログラマに提供しています。この API は通常 C++ か"
"らも全く同じように利用できるのですが、簡潔な呼び名にするために Python/C API "
"と名づけられています。根本的に異なる二つの目的から、 Python/C API が用いられ"
"ます。第一は、特定用途の *拡張モジュール (extension module)* 、すなわち "
"Python インタプリタを拡張する C で書かれたモジュールを記述する、という目的で"
"す。第二は、より大規模なアプリケーション内で Python を構成要素 (component) と"
"して利用するという目的です; このテクニックは、一般的にはアプリケーションへの "
"Python の埋め込み (:dfn:`embedding`) と呼びます。"
#: ../../c-api/intro.rst:20
msgid ""
"Writing an extension module is a relatively well-understood process, where a "
"\"cookbook\" approach works well. There are several tools that automate the "
"process to some extent. While people have embedded Python in other "
"applications since its early existence, the process of embedding Python is "
"less straightforward than writing an extension."
msgstr ""
"拡張モジュールの作成は比較的わかりやすいプロセスで、 \"手引書 (cookbook)\" 的"
"なアプローチでうまく実現できます。作業をある程度まで自動化してくれるツールも"
"いくつかあります。一方、他のアプリケーションへの Python の埋め込みは、Python "
"ができてから早い時期から行われてきましたが、拡張モジュールの作成に比べるとや"
"や難解です。"
#: ../../c-api/intro.rst:26
msgid ""
"Many API functions are useful independent of whether you're embedding or "
"extending Python; moreover, most applications that embed Python will need "
"to provide a custom extension as well, so it's probably a good idea to "
"become familiar with writing an extension before attempting to embed Python "
"in a real application."
msgstr ""
"多くの API 関数は、Python の埋め込みであるか拡張であるかに関わらず役立ちま"
"す; とはいえ、Python を埋め込んでいるほとんどのアプリケーションは、同時に自作"
"の拡張モジュールも提供する必要が生じることになるでしょうから、Python を実際に"
"アプリケーションに埋め込んでみる前に拡張モジュールの書き方に詳しくなっておく"
"のはよい考えだと思います。"
#: ../../c-api/intro.rst:34
msgid "Language version compatibility"
msgstr "言語バージョン互換性"
#: ../../c-api/intro.rst:36
msgid "Python's C API is compatible with C11 and C++11 versions of C and C++."
msgstr ""
"Pythonの C API は C11 や C++11 バージョンの C と C++ に互換性があります。"
#: ../../c-api/intro.rst:38
msgid ""
"This is a lower limit: the C API does not require features from later C/C++ "
"versions. You do *not* need to enable your compiler's \"c11 mode\"."
msgstr ""
#: ../../c-api/intro.rst:44
msgid "Coding standards"
msgstr "コーディング基準"
#: ../../c-api/intro.rst:46
msgid ""
"If you're writing C code for inclusion in CPython, you **must** follow the "
"guidelines and standards defined in :PEP:`7`. These guidelines apply "
"regardless of the version of Python you are contributing to. Following "
"these conventions is not necessary for your own third party extension "
"modules, unless you eventually expect to contribute them to Python."
msgstr ""
"CPython に含める C コードを書いている場合は、 :PEP:`7` のガイドラインと基準に"
"従わなければ **なりません** 。\n"
"このガイドラインは、コントリビュート対象の Python のバージョンに関係無く適用"
"されます。\n"
"自身のサードパーティーのモジュールでは、それをいつか Python にコントリビュー"
"トするつもりでなければ、この慣習に従う必要はありません。"
#: ../../c-api/intro.rst:56
msgid "Include Files"
msgstr "インクルードファイル"
#: ../../c-api/intro.rst:58
msgid ""
"All function, type and macro definitions needed to use the Python/C API are "
"included in your code by the following line::"
msgstr ""
"Python/C API を使うために必要な、関数、型およびマクロの全ての定義をインクルー"
"ドするには、以下の行::"
#: ../../c-api/intro.rst:61
msgid ""
"#define PY_SSIZE_T_CLEAN\n"
"#include <Python.h>"
msgstr ""
"#define PY_SSIZE_T_CLEAN\n"
"#include <Python.h>"
#: ../../c-api/intro.rst:64
msgid ""
"This implies inclusion of the following standard headers: ``<stdio.h>``, "
"``<string.h>``, ``<errno.h>``, ``<limits.h>``, ``<assert.h>`` and ``<stdlib."
"h>`` (if available)."
msgstr ""
"をソースコードに記述します。この行を記述すると、標準ヘッダ: ``<stdio.h>``, "
"``<string.h>``, ``<errno.h>``, ``<limits.h>``, ``<assert.h>``, ``<stdlib."
"h>`` を (利用できれば) インクルードします。"
#: ../../c-api/intro.rst:70
msgid ""
"Since Python may define some pre-processor definitions which affect the "
"standard headers on some systems, you *must* include :file:`Python.h` before "
"any standard headers are included."
msgstr ""
"Python は、システムによっては標準ヘッダの定義に影響するようなプリプロセッサ定"
"義を行っているので、 :file:`Python.h` をいずれの標準ヘッダよりも前にインク"
"ルード *せねばなりません* 。"
#: ../../c-api/intro.rst:74
msgid ""
"It is recommended to always define ``PY_SSIZE_T_CLEAN`` before including "
"``Python.h``. See :ref:`arg-parsing` for a description of this macro."
msgstr ""
"``Python.h`` をインクルードする前に、常に ``PY_SSIZE_T_CLEAN`` を定義すること"
"が推奨されます。\n"
"このマクロの解説については :ref:`arg-parsing` を参照してください。"
#: ../../c-api/intro.rst:77
msgid ""
"All user visible names defined by Python.h (except those defined by the "
"included standard headers) have one of the prefixes ``Py`` or ``_Py``. "
"Names beginning with ``_Py`` are for internal use by the Python "
"implementation and should not be used by extension writers. Structure member "
"names do not have a reserved prefix."
msgstr ""
"Python.h で定義されている、ユーザから見える名前全て (Python.h がインクルード"
"している標準ヘッダの名前は除きます) には、接頭文字列 ``Py`` または ``_Py`` が"
"付きます。``_Py`` で始まる名前は Python 実装で内部使用するための名前で、拡張"
"モジュールの作者は使ってはなりません。構造体のメンバには予約済みの接頭文字列"
"はありません。"
#: ../../c-api/intro.rst:84
msgid ""
"User code should never define names that begin with ``Py`` or ``_Py``. This "
"confuses the reader, and jeopardizes the portability of the user code to "
"future Python versions, which may define additional names beginning with one "
"of these prefixes."
msgstr ""
"API のユーザは、``Py`` や ``_Py`` で始まる名前を定義するコードを絶対に書いて"
"はなりません。\n"
"後からコードを読む人を混乱させたり、将来の Python のバージョンで同じ名前が定"
"義されて、ユーザの書いたコードの可搬性を危うくする可能性があります。"
#: ../../c-api/intro.rst:89
msgid ""
"The header files are typically installed with Python. On Unix, these are "
"located in the directories :file:`{prefix}/include/pythonversion/` and :file:"
"`{exec_prefix}/include/pythonversion/`, where :option:`prefix <--prefix>` "
"and :option:`exec_prefix <--exec-prefix>` are defined by the corresponding "
"parameters to Python's :program:`configure` script and *version* is ``'%d."
"%d' % sys.version_info[:2]``. On Windows, the headers are installed in :"
"file:`{prefix}/include`, where ``prefix`` is the installation directory "
"specified to the installer."
msgstr ""
"ヘッダファイル群は通常 Python と共にインストールされます。 Unixでは :file:"
"`{prefix}/include/pythonversion/` および :file:`{exec_prefix}/include/"
"pythonversion/` に置かれます。 :option:`prefix <--prefix>` と :option:"
"`exec_prefix <--exec-prefix>` は Python をビルドする際の :program:"
"`configure` スクリプトに与えたパラメタに対応し、 *version* は ``'%d.%d' % "
"sys.version_info[:2]`` に対応します。 Windows では、ヘッダは :file:`{prefix}/"
"include` に置かれます。 ``prefix`` はインストーラに指定したインストールディレ"
"クトリです。"
#: ../../c-api/intro.rst:98
msgid ""
"To include the headers, place both directories (if different) on your "
"compiler's search path for includes. Do *not* place the parent directories "
"on the search path and then use ``#include <pythonX.Y/Python.h>``; this will "
"break on multi-platform builds since the platform independent headers under :"
"option:`prefix <--prefix>` include the platform specific headers from :"
"option:`exec_prefix <--exec-prefix>`."
msgstr ""
"ヘッダをインクルードするには、各ヘッダの入ったディレクトリ (別々のディレクト"
"リの場合は両方) を、コンパイラがインクルードファイルを検索するためのパスに入"
"れます。親ディレクトリをサーチパスに入れて、 ``#include <pythonX.Y/Python."
"h>`` のようにしては *なりません* ; :option:`prefix <--prefix>` 内のプラット"
"フォームに依存しないヘッダは、 :option:`exec_prefix <--exec-prefix>` からプ"
"ラットフォーム依存のヘッダをインクルードしているので、このような操作を行うと"
"複数のプラットフォームでのビルドができなくなります。"
#: ../../c-api/intro.rst:105
msgid ""
"C++ users should note that although the API is defined entirely using C, the "
"header files properly declare the entry points to be ``extern \"C\"``. As a "
"result, there is no need to do anything special to use the API from C++."
msgstr ""
#: ../../c-api/intro.rst:111
msgid "Useful macros"
msgstr "便利なマクロ"
#: ../../c-api/intro.rst:113
msgid ""
"Several useful macros are defined in the Python header files. Many are "
"defined closer to where they are useful (for example, :c:macro:"
"`Py_RETURN_NONE`, :c:macro:`PyMODINIT_FUNC`). Others of a more general "
"utility are defined here. This is not necessarily a complete listing."
msgstr ""
#: ../../c-api/intro.rst:121
msgid ""
"If this macro is defined, then the current system is able to start threads."
msgstr ""
#: ../../c-api/intro.rst:123
msgid ""
"Currently, all systems supported by CPython (per :pep:`11`), with the "
"exception of some WebAssembly platforms, support starting threads."
msgstr ""
#: ../../c-api/intro.rst:130
msgid ""
"Like :samp:`getenv({s})`, but returns ``NULL`` if :option:`-E` was passed on "
"the command line (see :c:member:`PyConfig.use_environment`)."
msgstr ""
#: ../../c-api/intro.rst:135
msgid "Docstring macros"
msgstr ""
#: ../../c-api/intro.rst:139
msgid ""
"Creates a variable with name *name* that can be used in docstrings. If "
"Python is built without docstrings (:option:`--without-doc-strings`), the "
"value will be an empty string."
msgstr ""
#: ../../c-api/intro.rst:143 ../../c-api/intro.rst:160
#: ../../c-api/intro.rst:428
msgid "Example::"
msgstr "以下はプログラム例です::"
#: ../../c-api/intro.rst:145
msgid ""
"PyDoc_STRVAR(pop_doc, \"Remove and return the rightmost element.\");\n"
"\n"
"static PyMethodDef deque_methods[] = {\n"
" // ...\n"
" {\"pop\", (PyCFunction)deque_pop, METH_NOARGS, pop_doc},\n"
" // ...\n"
"}"
msgstr ""
"PyDoc_STRVAR(pop_doc, \"Remove and return the rightmost element.\");\n"
"\n"
"static PyMethodDef deque_methods[] = {\n"
" // ...\n"
" {\"pop\", (PyCFunction)deque_pop, METH_NOARGS, pop_doc},\n"
" // ...\n"
"}"
#: ../../c-api/intro.rst:153
msgid "Expands to :samp:`PyDoc_VAR({name}) = PyDoc_STR({str})`."
msgstr ""
#: ../../c-api/intro.rst:157
msgid ""
"Expands to the given input string, or an empty string if docstrings are "
"disabled (:option:`--without-doc-strings`)."
msgstr ""
#: ../../c-api/intro.rst:162
msgid ""
"static PyMethodDef pysqlite_row_methods[] = {\n"
" {\"keys\", (PyCFunction)pysqlite_row_keys, METH_NOARGS,\n"
" PyDoc_STR(\"Returns the keys of the row.\")},\n"
" {NULL, NULL}\n"
"};"
msgstr ""
"static PyMethodDef pysqlite_row_methods[] = {\n"
" {\"keys\", (PyCFunction)pysqlite_row_keys, METH_NOARGS,\n"
" PyDoc_STR(\"Returns the keys of the row.\")},\n"
" {NULL, NULL}\n"
"};"
#: ../../c-api/intro.rst:170
msgid ""
"Declares a static character array variable with the given *name*. Expands "
"to :samp:`static const char {name}[]`"
msgstr ""
#: ../../c-api/intro.rst:173 ../../c-api/intro.rst:314
#: ../../c-api/intro.rst:325
msgid "For example::"
msgstr "例えば::"
#: ../../c-api/intro.rst:175
msgid ""
"PyDoc_VAR(python_doc) = PyDoc_STR(\n"
" \"A genus of constricting snakes in the Pythonidae family native \"\n"
" \"to the tropics and subtropics of the Eastern Hemisphere.\");"
msgstr ""
#: ../../c-api/intro.rst:181
msgid "General utility macros"
msgstr ""
#: ../../c-api/intro.rst:183
msgid "The following macros are for common tasks not specific to Python."
msgstr ""
#: ../../c-api/intro.rst:187
msgid ""
"Use this for unused arguments in a function definition to silence compiler "
"warnings. Example: ``int func(int a, int Py_UNUSED(b)) { return a; }``."
msgstr ""
"コンパイラ警告を抑えるために関数定義の使用されない引数に使用してください。例"
"えば: ``int func(int a, int Py_UNUSED(b)) { return a; }`` 。"
#: ../../c-api/intro.rst:194
msgid ""
"Use a GCC attribute *name*, hiding it from compilers that don't support GCC "
"attributes (such as MSVC)."
msgstr ""
#: ../../c-api/intro.rst:197
msgid ""
"This expands to :samp:`__attribute__(({name)})` on a GCC compiler, and "
"expands to nothing on compilers that don't support GCC attributes."
msgstr ""
#: ../../c-api/intro.rst:202
msgid "Numeric utilities"
msgstr ""
#: ../../c-api/intro.rst:206
msgid "Return the absolute value of ``x``."
msgstr "``x`` の絶対値を返します。"
#: ../../c-api/intro.rst:208
msgid ""
"The argument may be evaluated more than once. Consequently, do not pass an "
"expression with side-effects directly to this macro."
msgstr ""
#: ../../c-api/intro.rst:212
msgid ""
"If the result cannot be represented (for example, if ``x`` has :c:macro:`!"
"INT_MIN` value for :c:expr:`int` type), the behavior is undefined."
msgstr ""
#: ../../c-api/intro.rst:216
msgid "Corresponds roughly to :samp:`(({x}) < 0 ? -({x}) : ({x}))`"
msgstr ""
#: ../../c-api/intro.rst:223
msgid "Return the larger or smaller of the arguments, respectively."
msgstr ""
#: ../../c-api/intro.rst:225
msgid ""
"Any arguments may be evaluated more than once. Consequently, do not pass an "
"expression with side-effects directly to this macro."
msgstr ""
#: ../../c-api/intro.rst:229
msgid ""
":c:macro:`!Py_MAX` corresponds roughly to :samp:`((({x}) > ({y})) ? ({x}) : "
"({y}))`."
msgstr ""
#: ../../c-api/intro.rst:236
msgid ""
"Similar to :samp:`{integer} >> {positions}`, but forces sign extension, as "
"the C standard does not define whether a right-shift of a signed integer "
"will perform sign extension or a zero-fill."
msgstr ""
#: ../../c-api/intro.rst:240
msgid ""
"*integer* should be any signed integer type. *positions* is the number of "
"positions to shift to the right."
msgstr ""
#: ../../c-api/intro.rst:243
msgid ""
"Both *integer* and *positions* can be evaluated more than once; "
"consequently, avoid directly passing a function call or some other operation "
"with side-effects to this macro. Instead, store the result as a variable and "
"then pass it."
msgstr ""
#: ../../c-api/intro.rst:248
msgid ""
"*type* is unused and only kept for backwards compatibility. Historically, "
"*type* was used to cast *integer*."
msgstr ""
#: ../../c-api/intro.rst:253
msgid ""
"This macro is now valid for all signed integer types, not just those for "
"which ``unsigned type`` is legal. As a result, *type* is no longer used."
msgstr ""
#: ../../c-api/intro.rst:259
msgid ""
"Argument must be a character or an integer in the range [-128, 127] or [0, "
"255]. This macro returns ``c`` cast to an ``unsigned char``."
msgstr ""
"引数は文字か、[-128, 127] あるいは [0, 255] の範囲の整数でなければなりませ"
"ん。\n"
"このマクロは ``符号なし文字`` にキャストした ``c`` を返します。"
#: ../../c-api/intro.rst:264
msgid "Assertion utilities"
msgstr ""
#: ../../c-api/intro.rst:268
msgid ""
"Use this when you have a code path that cannot be reached by design. For "
"example, in the ``default:`` clause in a ``switch`` statement for which all "
"possible values are covered in ``case`` statements. Use this in places "
"where you might be tempted to put an ``assert(0)`` or ``abort()`` call."
msgstr ""
#: ../../c-api/intro.rst:273
msgid ""
"In release mode, the macro helps the compiler to optimize the code, and "
"avoids a warning about unreachable code. For example, the macro is "
"implemented with ``__builtin_unreachable()`` on GCC in release mode."
msgstr ""
#: ../../c-api/intro.rst:277
msgid ""
"In debug mode, and on unsupported compilers, the macro expands to a call to :"
"c:func:`Py_FatalError`."
msgstr ""
#: ../../c-api/intro.rst:280
msgid ""
"A use for ``Py_UNREACHABLE()`` is following a call to a function that never "
"returns but that is not declared ``_Noreturn``."
msgstr ""
#: ../../c-api/intro.rst:283
msgid ""
"If a code path is very unlikely code but can be reached under exceptional "
"case, this macro must not be used. For example, under low memory condition "
"or if a system call returns a value out of the expected range. In this "
"case, it's better to report the error to the caller. If the error cannot be "
"reported to caller, :c:func:`Py_FatalError` can be used."
msgstr ""
#: ../../c-api/intro.rst:293
msgid ""
"Cast *value* to type *smaller* from type *larger*, validating that no "
"information was lost."
msgstr ""
#: ../../c-api/intro.rst:296
msgid ""
"On release builds of Python, this is roughly equivalent to :samp:"
"`(({smaller}) {value})` (in C++, :samp:`static_cast<{smaller}>({value})` "
"will be used instead)."
msgstr ""
#: ../../c-api/intro.rst:300
msgid ""
"On debug builds (implying that :c:macro:`Py_DEBUG` is defined), this asserts "
"that no information was lost with the cast from *larger* to *smaller*."
msgstr ""
#: ../../c-api/intro.rst:303
msgid ""
"*value*, *larger*, and *smaller* may all be evaluated more than once in the "
"expression; consequently, do not pass an expression with side-effects "
"directly to this macro."
msgstr ""
#: ../../c-api/intro.rst:309
msgid ""
"Asserts a compile-time condition *cond*, as a statement. The build will fail "
"if the condition is false or cannot be evaluated at compile time."
msgstr ""
#: ../../c-api/intro.rst:312
msgid "Corresponds roughly to :samp:`static_assert({cond})` on C23 and above."
msgstr ""
#: ../../c-api/intro.rst:316
msgid "Py_BUILD_ASSERT(sizeof(PyTime_t) == sizeof(int64_t));"
msgstr "Py_BUILD_ASSERT(sizeof(PyTime_t) == sizeof(int64_t));"
#: ../../c-api/intro.rst:322
msgid ""
"Asserts a compile-time condition *cond*, as an expression that evaluates to "
"``0``. The build will fail if the condition is false or cannot be evaluated "
"at compile time."
msgstr ""
#: ../../c-api/intro.rst:327
msgid ""
"#define foo_to_char(foo) \\\n"
" ((char *)(foo) + Py_BUILD_ASSERT_EXPR(offsetof(struct foo, string) == 0))"
msgstr ""
"#define foo_to_char(foo) \\\n"
" ((char *)(foo) + Py_BUILD_ASSERT_EXPR(offsetof(struct foo, string) == 0))"
#: ../../c-api/intro.rst:334
msgid "Type size utilities"
msgstr ""
#: ../../c-api/intro.rst:338
msgid "Compute the length of a statically allocated C array at compile time."
msgstr ""
#: ../../c-api/intro.rst:340
msgid ""
"The *array* argument must be a C array with a size known at compile time. "
"Passing an array with an unknown size, such as a heap-allocated array, will "
"result in a compilation error on some compilers, or otherwise produce "
"incorrect results."
msgstr ""
#: ../../c-api/intro.rst:345
msgid "This is roughly equivalent to::"
msgstr ""
#: ../../c-api/intro.rst:347
msgid "sizeof(array) / sizeof((array)[0])"
msgstr ""
#: ../../c-api/intro.rst:351
msgid "Return the size of a structure (*type*) *member* in bytes."
msgstr ""
#: ../../c-api/intro.rst:353
msgid "Corresponds roughly to :samp:`sizeof((({type} *)NULL)->{member})`."
msgstr ""
#: ../../c-api/intro.rst:359
msgid "Macro definition utilities"
msgstr ""
#: ../../c-api/intro.rst:363
msgid ""
"This is equivalent to :samp:`{X}`, which is useful for token-pasting in "
"macros, as macro expansions in *X* are forcefully evaluated by the "
"preprocessor."
msgstr ""
#: ../../c-api/intro.rst:369
msgid ""
"Convert ``x`` to a C string. For example, ``Py_STRINGIFY(123)`` returns "
"``\"123\"``."
msgstr ""
#: ../../c-api/intro.rst:376
msgid "Declaration utilities"
msgstr ""
#: ../../c-api/intro.rst:378
msgid ""
"The following macros can be used in declarations. They are most useful for "
"defining the C API itself, and have limited use for extension authors. Most "
"of them expand to compiler-specific spellings of common extensions to the C "
"language."
msgstr ""
#: ../../c-api/intro.rst:386
msgid ""
"Ask the compiler to always inline a static inline function. The compiler can "
"ignore it and decide to not inline the function."
msgstr ""
#: ../../c-api/intro.rst:389
msgid ""
"Corresponds to ``always_inline`` attribute in GCC and ``__forceinline`` in "
"MSVC."
msgstr ""
#: ../../c-api/intro.rst:392
msgid ""
"It can be used to inline performance critical static inline functions when "
"building Python in debug mode with function inlining disabled. For example, "
"MSC disables function inlining when building in debug mode."
msgstr ""
#: ../../c-api/intro.rst:396
msgid ""
"Marking blindly a static inline function with Py_ALWAYS_INLINE can result in "
"worse performances (due to increased code size for example). The compiler is "
"usually smarter than the developer for the cost/benefit analysis."
msgstr ""
#: ../../c-api/intro.rst:400
msgid ""
"If Python is :ref:`built in debug mode <debug-build>` (if the :c:macro:"
"`Py_DEBUG` macro is defined), the :c:macro:`Py_ALWAYS_INLINE` macro does "
"nothing."
msgstr ""
#: ../../c-api/intro.rst:403
msgid "It must be specified before the function return type. Usage::"
msgstr ""
#: ../../c-api/intro.rst:405
msgid "static inline Py_ALWAYS_INLINE int random(void) { return 4; }"
msgstr "static inline Py_ALWAYS_INLINE int random(void) { return 4; }"
#: ../../c-api/intro.rst:411
msgid ""
"Disable inlining on a function. For example, it reduces the C stack "
"consumption: useful on LTO+PGO builds which heavily inline code (see :issue:"
"`33720`)."
msgstr ""
#: ../../c-api/intro.rst:415
msgid ""
"Corresponds to the ``noinline`` attribute/specification on GCC and MSVC."
msgstr ""
#: ../../c-api/intro.rst:417
msgid "Usage::"
msgstr "使い方::"
#: ../../c-api/intro.rst:419
msgid "Py_NO_INLINE static int random(void) { return 4; }"
msgstr "Py_NO_INLINE static int random(void) { return 4; }"
#: ../../c-api/intro.rst:425
msgid ""
"Use this to declare APIs that were deprecated in a specific CPython version. "
"The macro must be placed before the symbol name."
msgstr ""
#: ../../c-api/intro.rst:430
msgid "Py_DEPRECATED(3.8) PyAPI_FUNC(int) Py_OldFunction(void);"
msgstr "Py_DEPRECATED(3.8) PyAPI_FUNC(int) Py_OldFunction(void);"
#: ../../c-api/intro.rst:432
msgid "MSVC support was added."
msgstr "MSVC サポートが追加されました。"
#: ../../c-api/intro.rst:437
msgid ""
"Declare a function returning the specified *type* using a fast-calling "
"qualifier for functions that are local to the current file. Semantically, "
"this is equivalent to :samp:`static {type}`."
msgstr ""
#: ../../c-api/intro.rst:443
msgid ""
"Equivalent to :c:macro:`Py_LOCAL` but additionally requests the function be "
"inlined."
msgstr ""
#: ../../c-api/intro.rst:448
msgid ""
"Macro used to declare a symbol as local to the shared library (hidden). On "
"supported platforms, it ensures the symbol is not exported."
msgstr ""
#: ../../c-api/intro.rst:451
msgid ""
"On compatible versions of GCC/Clang, it expands to "
"``__attribute__((visibility(\"hidden\")))``."
msgstr ""
#: ../../c-api/intro.rst:456
msgid ""
"Macro used to declare a symbol (function or data) as exported. On Windows, "
"this expands to ``__declspec(dllexport)``. On compatible versions of GCC/"
"Clang, it expands to ``__attribute__((visibility(\"default\")))``. This "
"macro is for defining the C API itself; extension modules should not use it."
msgstr ""
#: ../../c-api/intro.rst:465
msgid ""
"Macro used to declare a symbol as imported. On Windows, this expands to "
"``__declspec(dllimport)``. This macro is for defining the C API itself; "
"extension modules should not use it."
msgstr ""
#: ../../c-api/intro.rst:472
msgid ""
"Macro used by CPython to declare a function as part of the C API. Its "
"expansion depends on the platform and build configuration. This macro is "
"intended for defining CPython's C API itself; extension modules should not "
"use it for their own symbols."
msgstr ""
#: ../../c-api/intro.rst:480
msgid ""
"Macro used by CPython to declare a public global variable as part of the C "
"API. Its expansion depends on the platform and build configuration. This "
"macro is intended for defining CPython's C API itself; extension modules "
"should not use it for their own symbols."
msgstr ""
#: ../../c-api/intro.rst:487
msgid "Outdated macros"
msgstr ""
#: ../../c-api/intro.rst:489
msgid ""
"The following macros have been used to features that have been standardized "
"in C11."
msgstr ""
#: ../../c-api/intro.rst:494
msgid "Specify alignment to *num* bytes on compilers that support it."
msgstr ""
#: ../../c-api/intro.rst:496
msgid "Consider using the C11 standard ``_Alignas`` specifier over this macro."
msgstr ""
#: ../../c-api/intro.rst:501
msgid ""
"Use *number* as a ``long long`` or ``unsigned long long`` integer literal, "
"respectively."
msgstr ""
#: ../../c-api/intro.rst:504
msgid ""
"Expands to *number* followed by ``LL`` or ``LLU``, respectively, but will "
"expand to some compiler-specific suffixes on some older compilers."
msgstr ""
#: ../../c-api/intro.rst:507
msgid "Consider using the C99 standard suffixes ``LL`` and ``LLU`` directly."
msgstr ""
#: ../../c-api/intro.rst:511
msgid ""
"This is a :term:`soft deprecated` alias to :c:func:`!memcpy`. Use :c:func:`!"
"memcpy` directly instead."
msgstr ""
#: ../../c-api/intro.rst:514
msgid "The macro is :term:`soft deprecated`."
msgstr ""
#: ../../c-api/intro.rst:519
msgid ""
"This is a :term:`soft deprecated` alias to the C99-standard ``va_copy`` "
"function."
msgstr ""
#: ../../c-api/intro.rst:522
msgid ""
"Historically, this would use a compiler-specific method to copy a "
"``va_list``."
msgstr ""
#: ../../c-api/intro.rst:524
msgid "This is now an alias to ``va_copy``."
msgstr ""
#: ../../c-api/intro.rst:531
msgid "Objects, Types and Reference Counts"
msgstr "オブジェクト、型および参照カウント"
#: ../../c-api/intro.rst:535
msgid ""
"Most Python/C API functions have one or more arguments as well as a return "
"value of type :c:expr:`PyObject*`. This type is a pointer to an opaque data "
"type representing an arbitrary Python object. Since all Python object types "
"are treated the same way by the Python language in most situations (e.g., "
"assignments, scope rules, and argument passing), it is only fitting that "
"they should be represented by a single C type. Almost all Python objects "
"live on the heap: you never declare an automatic or static variable of type :"
"c:type:`PyObject`, only pointer variables of type :c:expr:`PyObject*` can "
"be declared. The sole exception are the type objects; since these must "
"never be deallocated, they are typically static :c:type:`PyTypeObject` "
"objects."
msgstr ""
"Python/C API 関数は、 :c:expr:`PyObject*` 型の一つ以上の引数と戻り値を持ちま"
"す。この型は、任意の Python オブジェクトを表現する不透明 (opaque) なデータ型"
"へのポインタです。 Python 言語は、全ての Python オブジェクト型をほとんどの状"
"況 (例えば代入、スコープ規則 (scope rule)、引数渡し) で同様に扱います。ほとん"
"ど全ての Python オブジェクトはヒープ (heap) 上に置かれます: このため、 :c:"
"type:`PyObject` 型のオブジェクトは、自動記憶 (automatic) としても静的記憶 "
"(static) としても宣言できません。 :c:expr:`PyObject*` 型のポインタ変数のみ宣"
"言できます。唯一の例外は、型オブジェクトです; 型オブジェクトはメモリ解放 "
"(deallocate) してはならないので、通常は静的記憶の :c:type:`PyTypeObject` オブ"
"ジェクトにします。"
#: ../../c-api/intro.rst:546
msgid ""
"All Python objects (even Python integers) have a :dfn:`type` and a :dfn:"
"`reference count`. An object's type determines what kind of object it is (e."
"g., an integer, a list, or a user-defined function; there are many more as "
"explained in :ref:`types`). For each of the well-known types there is a "
"macro to check whether an object is of that type; for instance, "
"``PyList_Check(a)`` is true if (and only if) the object pointed to by *a* is "
"a Python list."
msgstr ""
"全ての Python オブジェクトには (Python 整数型ですら) 型 (:dfn:`type`) と参照"
"カウント (:dfn:`reference count`) があります。あるオブジェクトの型は、そのオ"
"ブジェクトがどの種類のオブジェクトか (例えば整数、リスト、ユーザ定義関数、な"
"ど; その他多数については :ref:`types` で説明しています) を決定します。よく知"
"られている型については、各々マクロが存在して、あるオブジェクトがその型かどう"
"か調べられます; 例えば、 ``PyList_Check(a)`` は、 *a* で示されたオブジェクト"
"が Python リスト型のとき (かつそのときに限り) 真値を返します。"
#: ../../c-api/intro.rst:557
msgid "Reference Counts"
msgstr "参照カウント法"
#: ../../c-api/intro.rst:559
msgid ""
"The reference count is important because today's computers have a finite "
"(and often severely limited) memory size; it counts how many different "
"places there are that have a :term:`strong reference` to an object. Such a "
"place could be another object, or a global (or static) C variable, or a "
"local variable in some C function. When the last :term:`strong reference` to "
"an object is released (i.e. its reference count becomes zero), the object is "
"deallocated. If it contains references to other objects, those references "
"are released. Those other objects may be deallocated in turn, if there are "
"no more references to them, and so on. (There's an obvious problem with "
"objects that reference each other here; for now, the solution is \"don't do "
"that.\")"
msgstr ""
#: ../../c-api/intro.rst:576
msgid ""
"Reference counts are always manipulated explicitly. The normal way is to "
"use the macro :c:func:`Py_INCREF` to take a new reference to an object (i.e. "
"increment its reference count by one), and :c:func:`Py_DECREF` to release "
"that reference (i.e. decrement the reference count by one). The :c:func:"
"`Py_DECREF` macro is considerably more complex than the incref one, since it "
"must check whether the reference count becomes zero and then cause the "
"object's deallocator to be called. The deallocator is a function pointer "
"contained in the object's type structure. The type-specific deallocator "
"takes care of releasing references for other objects contained in the object "
"if this is a compound object type, such as a list, as well as performing any "
"additional finalization that's needed. There's no chance that the reference "
"count can overflow; at least as many bits are used to hold the reference "
"count as there are distinct memory locations in virtual memory (assuming "
"``sizeof(Py_ssize_t) >= sizeof(void*)``). Thus, the reference count "
"increment is a simple operation."
msgstr ""
#: ../../c-api/intro.rst:592
msgid ""
"It is not necessary to hold a :term:`strong reference` (i.e. increment the "
"reference count) for every local variable that contains a pointer to an "
"object. In theory, the object's reference count goes up by one when the "
"variable is made to point to it and it goes down by one when the variable "
"goes out of scope. However, these two cancel each other out, so at the end "
"the reference count hasn't changed. The only real reason to use the "
"reference count is to prevent the object from being deallocated as long as "
"our variable is pointing to it. If we know that there is at least one "
"other reference to the object that lives at least as long as our variable, "
"there is no need to take a new :term:`strong reference` (i.e. increment the "
"reference count) temporarily. An important situation where this arises is in "
"objects that are passed as arguments to C functions in an extension module "
"that are called from Python; the call mechanism guarantees to hold a "
"reference to every argument for the duration of the call."
msgstr ""
#: ../../c-api/intro.rst:608
msgid ""
"However, a common pitfall is to extract an object from a list and hold on to "
"it for a while without taking a new reference. Some other operation might "
"conceivably remove the object from the list, releasing that reference, and "
"possibly deallocating it. The real danger is that innocent-looking "
"operations may invoke arbitrary Python code which could do this; there is a "
"code path which allows control to flow back to the user from a :c:func:"
"`Py_DECREF`, so almost any operation is potentially dangerous."
msgstr ""
#: ../../c-api/intro.rst:616
msgid ""
"A safe approach is to always use the generic operations (functions whose "
"name begins with ``PyObject_``, ``PyNumber_``, ``PySequence_`` or "
"``PyMapping_``). These operations always create a new :term:`strong "
"reference` (i.e. increment the reference count) of the object they return. "
"This leaves the caller with the responsibility to call :c:func:`Py_DECREF` "
"when they are done with the result; this soon becomes second nature."
msgstr ""
#: ../../c-api/intro.rst:627
msgid "Reference Count Details"
msgstr "参照カウントの詳細"
#: ../../c-api/intro.rst:629
msgid ""
"The reference count behavior of functions in the Python/C API is best "
"explained in terms of *ownership of references*. Ownership pertains to "
"references, never to objects (objects are not owned: they are always "
"shared). \"Owning a reference\" means being responsible for calling "
"Py_DECREF on it when the reference is no longer needed. Ownership can also "
"be transferred, meaning that the code that receives ownership of the "
"reference then becomes responsible for eventually releasing it by calling :c:"
"func:`Py_DECREF` or :c:func:`Py_XDECREF` when it's no longer needed---or "
"passing on this responsibility (usually to its caller). When a function "
"passes ownership of a reference on to its caller, the caller is said to "
"receive a *new* reference. When no ownership is transferred, the caller is "
"said to *borrow* the reference. Nothing needs to be done for a :term:"
"`borrowed reference`."
msgstr ""
#: ../../c-api/intro.rst:642
msgid ""
"Conversely, when a calling function passes in a reference to an object, "
"there are two possibilities: the function *steals* a reference to the "
"object, or it does not. *Stealing a reference* means that when you pass a "
"reference to a function, that function assumes that it now owns that "
"reference, and you are not responsible for it any longer."
msgstr ""
"逆に、ある関数呼び出しで、あるオブジェクトへの参照を呼び出される関数に渡す際"
"には、二つの可能性: 関数がオブジェクトへの参照を *盗み取る* (steal) 場合と、"
"そうでない場合があります。*参照を盗む* とは、関数に参照を渡したときに、参照の"
"所有者がその関数になったと仮定し、関数の呼び出し元には所有権がなくなるという"
"ことです。"
#: ../../c-api/intro.rst:652
msgid ""
"Few functions steal references; the two notable exceptions are :c:func:"
"`PyList_SetItem` and :c:func:`PyTuple_SetItem`, which steal a reference to "
"the item (but not to the tuple or list into which the item is put!). These "
"functions were designed to steal a reference because of a common idiom for "
"populating a tuple or list with newly created objects; for example, the code "
"to create the tuple ``(1, 2, \"three\")`` could look like this (forgetting "
"about error handling for the moment; a better way to code this is shown "
"below)::"
msgstr ""
"参照を盗み取る関数はほとんどありません; 例外としてよく知られているのは、 :c:"
"func:`PyList_SetItem` と :c:func:`PyTuple_SetItem` で、これらはシーケンスに入"
"れる要素に対する参照を盗み取ります (しかし、要素の入る先のタプルやリストの参"
"照は盗み取りません!)。これらの関数は、リストやタプルの中に新たに作成されたオ"
"ブジェクトを入れていく際の常套的な書き方をしやすくするために、参照を盗み取る"
"ように設計されています; 例えば、 ``(1, 2, \"three\")`` というタプルを生成する"
"コードは以下のようになります (とりあえず例外処理のことは忘れておきます; もっ"
"とよい書き方を後で示します)::"
#: ../../c-api/intro.rst:660
msgid ""
"PyObject *t;\n"
"\n"
"t = PyTuple_New(3);\n"
"PyTuple_SetItem(t, 0, PyLong_FromLong(1L));\n"
"PyTuple_SetItem(t, 1, PyLong_FromLong(2L));\n"
"PyTuple_SetItem(t, 2, PyUnicode_FromString(\"three\"));"
msgstr ""
#: ../../c-api/intro.rst:667
msgid ""
"Here, :c:func:`PyLong_FromLong` returns a new reference which is immediately "
"stolen by :c:func:`PyTuple_SetItem`. When you want to keep using an object "
"although the reference to it will be stolen, use :c:func:`Py_INCREF` to grab "
"another reference before calling the reference-stealing function."
msgstr ""
"ここで、 :c:func:`PyLong_FromLong` は新しい参照を返し、すぐに :c:func:"
"`PyTuple_SetItem` に盗まれます。参照が盗まれた後もそのオブジェクトを利用した"
"い場合は、参照盗む関数を呼び出す前に、 :c:func:`Py_INCREF` を利用してもう一つ"
"の参照を取得してください。"
#: ../../c-api/intro.rst:672
msgid ""
"Incidentally, :c:func:`PyTuple_SetItem` is the *only* way to set tuple "
"items; :c:func:`PySequence_SetItem` and :c:func:`PyObject_SetItem` refuse to "