-
-
Notifications
You must be signed in to change notification settings - Fork 32
/
Copy pathintro.po
1392 lines (1252 loc) · 65.7 KB
/
intro.po
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-2025, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Yusuke Miyazaki <miyazaki.dev@gmail.com>, 2021
# Osamu NAKAMURA, 2023
# Masato HASHIMOTO <cabezon.hashimoto@gmail.com>, 2023
# tomo, 2023
# Nozomu Kaneko <nozom.kaneko@gmail.com>, 2024
# Arihiro TAKASE, 2024
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.13\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-04-11 14:19+0000\n"
"PO-Revision-Date: 2021-06-28 00:49+0000\n"
"Last-Translator: Arihiro TAKASE, 2024\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 "Coding standards"
msgstr "コーディング基準"
#: ../../c-api/intro.rst:36
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:46
msgid "Include Files"
msgstr "インクルードファイル"
#: ../../c-api/intro.rst:48
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:51
msgid ""
"#define PY_SSIZE_T_CLEAN\n"
"#include <Python.h>"
msgstr ""
#: ../../c-api/intro.rst:54
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:60
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:64
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:67
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:74
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:79
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:88
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:95
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:101
msgid "Useful macros"
msgstr "便利なマクロ"
#: ../../c-api/intro.rst:103
msgid ""
"Several useful macros are defined in the Python header files. Many are "
"defined closer to where they are useful (e.g. :c:macro:`Py_RETURN_NONE`). "
"Others of a more general utility are defined here. This is not necessarily "
"a complete listing."
msgstr ""
"Python のヘッダーファイルには便利なマクロがいくつか定義されています。\n"
"多くのマクロは、それが役に立つところ (例えば、 :c:macro:`Py_RETURN_NONE`) の"
"近くに定義があります。\n"
"より一般的な使われかたをする他のマクロはこれらのヘッダーファイルに定義されて"
"います。\n"
"ただし、ここで完全に列挙されているとは限りません。"
#: ../../c-api/intro.rst:110
msgid ""
"Declare an extension module ``PyInit`` initialization function. The function "
"return type is :c:expr:`PyObject*`. The macro declares any special linkage "
"declarations required by the platform, and for C++ declares the function as "
"``extern \"C\"``."
msgstr ""
#: ../../c-api/intro.rst:115
msgid ""
"The initialization function must be named :samp:`PyInit_{name}`, where "
"*name* is the name of the module, and should be the only non-\\ ``static`` "
"item defined in the module file. Example::"
msgstr ""
#: ../../c-api/intro.rst:119
msgid ""
"static struct PyModuleDef spam_module = {\n"
" PyModuleDef_HEAD_INIT,\n"
" .m_name = \"spam\",\n"
" ...\n"
"};\n"
"\n"
"PyMODINIT_FUNC\n"
"PyInit_spam(void)\n"
"{\n"
" return PyModule_Create(&spam_module);\n"
"}"
msgstr ""
#: ../../c-api/intro.rst:134
msgid "Return the absolute value of ``x``."
msgstr "``x`` の絶対値を返します。"
#: ../../c-api/intro.rst:140
msgid ""
"Ask the compiler to always inline a static inline function. The compiler can "
"ignore it and decides to not inline the function."
msgstr ""
#: ../../c-api/intro.rst:143
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:147
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:151
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:154
msgid "It must be specified before the function return type. Usage::"
msgstr ""
#: ../../c-api/intro.rst:156
msgid "static inline Py_ALWAYS_INLINE int random(void) { return 4; }"
msgstr ""
#: ../../c-api/intro.rst:162
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:167
msgid ""
"Use this for deprecated declarations. The macro must be placed before the "
"symbol name."
msgstr ""
#: ../../c-api/intro.rst:170 ../../c-api/intro.rst:256
#: ../../c-api/intro.rst:274
msgid "Example::"
msgstr "以下はプログラム例です::"
#: ../../c-api/intro.rst:172
msgid "Py_DEPRECATED(3.8) PyAPI_FUNC(int) Py_OldFunction(void);"
msgstr ""
#: ../../c-api/intro.rst:174
msgid "MSVC support was added."
msgstr "MSVC サポートが追加されました。"
#: ../../c-api/intro.rst:179
msgid ""
"Like ``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:184
msgid "Return the maximum value between ``x`` and ``y``."
msgstr "``x`` と ``y`` の最大値を返します。"
#: ../../c-api/intro.rst:190
msgid "Return the size of a structure (``type``) ``member`` in bytes."
msgstr "(``type``) 構造体の ``member`` のサイズをバイト単位で返します。"
#: ../../c-api/intro.rst:196
msgid "Return the minimum value between ``x`` and ``y``."
msgstr "``x`` と ``y`` の最小値を返します。"
#: ../../c-api/intro.rst:202
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:206
msgid "Usage::"
msgstr "使い方::"
#: ../../c-api/intro.rst:208
msgid "Py_NO_INLINE static int random(void) { return 4; }"
msgstr ""
#: ../../c-api/intro.rst:214
msgid ""
"Convert ``x`` to a C string. E.g. ``Py_STRINGIFY(123)`` returns ``\"123\"``."
msgstr ""
"``x`` を C 文字列へ変換します。\n"
"例えば、 ``Py_STRINGIFY(123)`` は ``\"123\"`` を返します。"
#: ../../c-api/intro.rst:221
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:226
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:230
msgid ""
"A use for ``Py_UNREACHABLE()`` is following a call a function that never "
"returns but that is not declared :c:macro:`_Py_NO_RETURN`."
msgstr ""
#: ../../c-api/intro.rst:233
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:243
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 ""
#: ../../c-api/intro.rst:250
msgid ""
"Creates a variable with name ``name`` that can be used in docstrings. If "
"Python is built without docstrings, the value will be empty."
msgstr ""
#: ../../c-api/intro.rst:253
msgid ""
"Use :c:macro:`PyDoc_STRVAR` for docstrings to support building Python "
"without docstrings, as specified in :pep:`7`."
msgstr ""
#: ../../c-api/intro.rst:258
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 ""
#: ../../c-api/intro.rst:268
msgid ""
"Creates a docstring for the given input string or an empty string if "
"docstrings are disabled."
msgstr ""
#: ../../c-api/intro.rst:271
msgid ""
"Use :c:macro:`PyDoc_STR` in specifying docstrings to support building Python "
"without docstrings, as specified in :pep:`7`."
msgstr ""
#: ../../c-api/intro.rst:276
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 ""
#: ../../c-api/intro.rst:286
msgid "Objects, Types and Reference Counts"
msgstr "オブジェクト、型および参照カウント"
#: ../../c-api/intro.rst:290
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:301
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:312
msgid "Reference Counts"
msgstr "参照カウント法"
#: ../../c-api/intro.rst:314
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:331
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:347
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:363
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:371
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:382
msgid "Reference Count Details"
msgstr "参照カウントの詳細"
#: ../../c-api/intro.rst:384
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:397
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:407
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:415
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:422
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:427
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 "
"do this since tuples are an immutable data type. You should only use :c:"
"func:`PyTuple_SetItem` for tuples that you are creating yourself."
msgstr ""
"ちなみに、 :c:func:`PyTuple_SetItem` はタプルに値をセットするための *唯一の* "
"方法です; タプルは変更不能なデータ型なので、 :c:func:`PySequence_SetItem` "
"や :c:func:`PyObject_SetItem` を使うと上の操作は拒否されてしまいます。自分で"
"タプルの値を入れていくつもりなら、 :c:func:`PyTuple_SetItem` だけしか使えませ"
"ん。"
#: ../../c-api/intro.rst:432
msgid ""
"Equivalent code for populating a list can be written using :c:func:"
"`PyList_New` and :c:func:`PyList_SetItem`."
msgstr ""
"同じく、リストに値を入れていくコードは :c:func:`PyList_New` と :c:func:"
"`PyList_SetItem` で書けます。"
#: ../../c-api/intro.rst:435
msgid ""
"However, in practice, you will rarely use these ways of creating and "
"populating a tuple or list. There's a generic function, :c:func:"
"`Py_BuildValue`, that can create most common objects from C values, directed "
"by a :dfn:`format string`. For example, the above two blocks of code could "
"be replaced by the following (which also takes care of the error checking)::"
msgstr ""
"しかし実際には、タプルやリストを生成して値を入れる際には、上記のような方法は"
"ほとんど使いません。より汎用性のある関数、 :c:func:`Py_BuildValue` があり、ほ"
"とんどの主要なオブジェクトをフォーマット文字列 :dfn:`format string` の指定に"
"基づいて C の値から生成できます。例えば、上の二種類のコードブロックは、以下の"
"ように置き換えられます (エラーチェックにも配慮しています)::"
#: ../../c-api/intro.rst:441
msgid ""
"PyObject *tuple, *list;\n"
"\n"
"tuple = Py_BuildValue(\"(iis)\", 1, 2, \"three\");\n"
"list = Py_BuildValue(\"[iis]\", 1, 2, \"three\");"
msgstr ""
#: ../../c-api/intro.rst:446
msgid ""
"It is much more common to use :c:func:`PyObject_SetItem` and friends with "
"items whose references you are only borrowing, like arguments that were "
"passed in to the function you are writing. In that case, their behaviour "
"regarding references is much saner, since you don't have to take a new "
"reference just so you can give that reference away (\"have it be stolen\"). "
"For example, this function sets all items of a list (actually, any mutable "
"sequence) to a given item::"
msgstr ""
#: ../../c-api/intro.rst:453
msgid ""
"int\n"
"set_all(PyObject *target, PyObject *item)\n"
"{\n"
" Py_ssize_t i, n;\n"
"\n"
" n = PyObject_Length(target);\n"
" if (n < 0)\n"
" return -1;\n"
" for (i = 0; i < n; i++) {\n"
" PyObject *index = PyLong_FromSsize_t(i);\n"
" if (!index)\n"
" return -1;\n"
" if (PyObject_SetItem(target, index, item) < 0) {\n"
" Py_DECREF(index);\n"
" return -1;\n"
" }\n"
" Py_DECREF(index);\n"
" }\n"
" return 0;\n"
"}"
msgstr ""
#: ../../c-api/intro.rst:476
msgid ""
"The situation is slightly different for function return values. While "
"passing a reference to most functions does not change your ownership "
"responsibilities for that reference, many functions that return a reference "
"to an object give you ownership of the reference. The reason is simple: in "
"many cases, the returned object is created on the fly, and the reference "
"you get is the only reference to the object. Therefore, the generic "
"functions that return object references, like :c:func:`PyObject_GetItem` "
"and :c:func:`PySequence_GetItem`, always return a new reference (the caller "
"becomes the owner of the reference)."
msgstr ""
"関数の戻り値の場合には、状況は少し異なります。ほとんどの関数については、参照"
"を渡してもその参照に対する所有権が変わることがない一方で、あるオブジェクトに"
"対する参照を返すような多くの関数は、参照に対する所有権を呼び出し側に与えま"
"す。理由は簡単です: 多くの場合、関数が返すオブジェクトはその場で (on the "
"fly) 生成されるため、呼び出し側が得る参照は生成されたオブジェクトに対する唯一"
"の参照になるからです。従って、 :c:func:`PyObject_GetItem` や :c:func:"
"`PySequence_GetItem` のように、オブジェクトに対する参照を返す汎用の関数は、常"
"に新たな参照を返します (呼び出し側が参照の所有者になります)。"
#: ../../c-api/intro.rst:485
msgid ""
"It is important to realize that whether you own a reference returned by a "
"function depends on which function you call only --- *the plumage* (the type "
"of the object passed as an argument to the function) *doesn't enter into it!"
"* Thus, if you extract an item from a list using :c:func:`PyList_GetItem`, "
"you don't own the reference --- but if you obtain the same item from the "
"same list using :c:func:`PySequence_GetItem` (which happens to take exactly "
"the same arguments), you do own a reference to the returned object."
msgstr ""
"重要なのは、関数が返す参照の所有権を持てるかどうかは、どの関数を呼び出すかだ"
"けによる、と理解することです --- 関数呼び出し時の *お飾り* (関数に引数として"
"渡したオブジェクトの型) は *この問題には関係ありません!* 従って、 :c:func:"
"`PyList_GetItem` を使ってリスト内の要素を得た場合には、参照の所有者にはなりま"
"せん --- が、同じ要素を同じリストから :c:func:`PySequence_GetItem` (図らずも"
"この関数は全く同じ引数をとります) を使って取り出すと、返されたオブジェクトに"
"対する参照を得ます。"
#: ../../c-api/intro.rst:497
msgid ""
"Here is an example of how you could write a function that computes the sum "
"of the items in a list of integers; once using :c:func:`PyList_GetItem`, "
"and once using :c:func:`PySequence_GetItem`. ::"
msgstr ""
"以下は、整数からなるリストに対して各要素の合計を計算する関数をどのようにして"
"書けるかを示した例です; 一つは :c:func:`PyList_GetItem` を使っていて、もう一"
"つは :c:func:`PySequence_GetItem` を使っています。 ::"
#: ../../c-api/intro.rst:501
msgid ""
"long\n"
"sum_list(PyObject *list)\n"
"{\n"
" Py_ssize_t i, n;\n"
" long total = 0, value;\n"
" PyObject *item;\n"
"\n"
" n = PyList_Size(list);\n"
" if (n < 0)\n"
" return -1; /* Not a list */\n"
" for (i = 0; i < n; i++) {\n"
" item = PyList_GetItem(list, i); /* Can't fail */\n"
" if (!PyLong_Check(item)) continue; /* Skip non-integers */\n"
" value = PyLong_AsLong(item);\n"
" if (value == -1 && PyErr_Occurred())\n"
" /* Integer too big to fit in a C long, bail out */\n"
" return -1;\n"
" total += value;\n"
" }\n"
" return total;\n"
"}"
msgstr ""
#: ../../c-api/intro.rst:527
msgid ""
"long\n"
"sum_sequence(PyObject *sequence)\n"
"{\n"
" Py_ssize_t i, n;\n"
" long total = 0, value;\n"
" PyObject *item;\n"
" n = PySequence_Length(sequence);\n"
" if (n < 0)\n"
" return -1; /* Has no length */\n"
" for (i = 0; i < n; i++) {\n"
" item = PySequence_GetItem(sequence, i);\n"
" if (item == NULL)\n"
" return -1; /* Not a sequence, or other failure */\n"
" if (PyLong_Check(item)) {\n"
" value = PyLong_AsLong(item);\n"
" Py_DECREF(item);\n"
" if (value == -1 && PyErr_Occurred())\n"
" /* Integer too big to fit in a C long, bail out */\n"
" return -1;\n"
" total += value;\n"
" }\n"
" else {\n"
" Py_DECREF(item); /* Discard reference ownership */\n"
" }\n"
" }\n"
" return total;\n"
"}"
msgstr ""
#: ../../c-api/intro.rst:561
msgid "Types"
msgstr "型"
#: ../../c-api/intro.rst:563
msgid ""
"There are few other data types that play a significant role in the Python/C "
"API; most are simple C types such as :c:expr:`int`, :c:expr:`long`, :c:expr:"
"`double` and :c:expr:`char*`. A few structure types are used to describe "
"static tables used to list the functions exported by a module or the data "
"attributes of a new object type, and another is used to describe the value "
"of a complex number. These will be discussed together with the functions "
"that use them."
msgstr ""
"他にも Python/C API において重要な役割を持つデータ型がいくつかあります; ほと"
"んどは :c:expr:`int`, :c:expr:`long`, :c:expr:`double`, および :c:expr:"
"`char*` といった、単なる C のデータ型です。また、モジュールで公開している関数"
"を列挙する際に用いられる静的なテーブルや、新しいオブジェクト型におけるデータ"
"属性を記述したり、複素数の値を記述したりするために構造体をいくつか使っていま"
"す。これらの型については、その型を使う関数とともに説明してゆきます。"
#: ../../c-api/intro.rst:573
msgid ""
"A signed integral type such that ``sizeof(Py_ssize_t) == sizeof(size_t)``. "
"C99 doesn't define such a thing directly (size_t is an unsigned integral "
"type). See :pep:`353` for details. ``PY_SSIZE_T_MAX`` is the largest "
"positive value of type :c:type:`Py_ssize_t`."
msgstr ""
#: ../../c-api/intro.rst:582
msgid "Exceptions"
msgstr "例外"
#: ../../c-api/intro.rst:584
msgid ""
"The Python programmer only needs to deal with exceptions if specific error "
"handling is required; unhandled exceptions are automatically propagated to "
"the caller, then to the caller's caller, and so on, until they reach the top-"
"level interpreter, where they are reported to the user accompanied by a "
"stack traceback."
msgstr ""
"Python プログラマは、特定のエラー処理が必要なときだけしか例外を扱う必要はあり"
"ません; 処理しなかった例外は、処理の呼び出し側、そのまた呼び出し側、といった"
"具合に、トップレベルのインタプリタ層まで自動的に伝播します。インタプリタ層"
"は、スタックトレースバックと合わせて例外をユーザに報告します。"
#: ../../c-api/intro.rst:592
msgid ""
"For C programmers, however, error checking always has to be explicit. All "
"functions in the Python/C API can raise exceptions, unless an explicit claim "
"is made otherwise in a function's documentation. In general, when a "
"function encounters an error, it sets an exception, discards any object "
"references that it owns, and returns an error indicator. If not documented "
"otherwise, this indicator is either ``NULL`` or ``-1``, depending on the "
"function's return type. A few functions return a Boolean true/false result, "
"with false indicating an error. Very few functions return no explicit error "
"indicator or have an ambiguous return value, and require explicit testing "
"for errors with :c:func:`PyErr_Occurred`. These exceptions are always "
"explicitly documented."
msgstr ""
"ところが、 C プログラマの場合、エラーチェックは常に明示的に行わねばなりませ"
"ん。 Python/C API の全ての関数は、関数のドキュメントで明確に説明がない限り例"
"外を発行する可能性があります。一般的な話として、ある関数が何らかのエラーに遭"
"遇すると、関数は例外を設定して、関数内における参照の所有権を全て放棄し、エ"
"ラー値 (error indicator) を返します。ドキュメントに書かれてない場合、このエ"
"ラー値は関数の戻り値の型によって、 ``NULL`` か ``-1`` のどちらかになります。"
"いくつかの関数ではブール型で真/偽を返し、偽はエラーを示します。きわめて少数の"
"関数では明確なエラー指標を返さなかったり、あいまいな戻り値を返したりするの"
"で、 :c:func:`PyErr_Occurred` で明示的にエラーテストを行う必要があります。こ"
"れらの例外は常に明示的にドキュメント化されます。"
#: ../../c-api/intro.rst:607
msgid ""
"Exception state is maintained in per-thread storage (this is equivalent to "
"using global storage in an unthreaded application). A thread can be in one "
"of two states: an exception has occurred, or not. The function :c:func:"
"`PyErr_Occurred` can be used to check for this: it returns a borrowed "
"reference to the exception type object when an exception has occurred, and "
"``NULL`` otherwise. There are a number of functions to set the exception "
"state: :c:func:`PyErr_SetString` is the most common (though not the most "
"general) function to set the exception state, and :c:func:`PyErr_Clear` "
"clears the exception state."
msgstr ""
"例外時の状態情報 (exception state)は、スレッド単位に用意された記憶領域 (per-"
"thread storage) 内で管理されます (この記憶領域は、スレッドを使わないアプリ"
"ケーションではグローバルな記憶領域と同じです)。一つのスレッドは二つの状態のど"
"ちらか: 例外が発生したか、まだ発生していないか、をとります。関数 :c:func:"
"`PyErr_Occurred` を使うと、この状態を調べられます: この関数は例外が発生した際"
"にはその例外型オブジェクトに対する借用参照 (borrowed reference) を返し、そう"
"でないときには ``NULL`` を返します。例外状態を設定する関数は数多くあります: :"
"c:func:`PyErr_SetString` はもっともよく知られている (が、もっとも汎用性のな"
"い) 例外を設定するための関数で、 :c:func:`PyErr_Clear` は例外状態情報を消し去"
"る関数です。"
#: ../../c-api/intro.rst:617
msgid ""
"The full exception state consists of three objects (all of which can be "
"``NULL``): the exception type, the corresponding exception value, and the "
"traceback. These have the same meanings as the Python result of ``sys."
"exc_info()``; however, they are not the same: the Python objects represent "
"the last exception being handled by a Python :keyword:`try` ... :keyword:"
"`except` statement, while the C level exception state only exists while an "
"exception is being passed on between C functions until it reaches the Python "
"bytecode interpreter's main loop, which takes care of transferring it to "
"``sys.exc_info()`` and friends."
msgstr ""
"完全な例外状態情報は、3 つのオブジェクト: 例外の型、例外の値、そしてトレース"
"バック、からなります (どのオブジェクトも ``NULL`` を取り得ます)。これらの情"
"報は、 Python の ``sys.exc_info()`` の結果と同じ意味を持ちます; とはいえ、 C "
"と Python の例外状態情報は全く同じではありません: Python における例外オブジェ"
"クトは、Python の :keyword:`try` ... :keyword:`except` 文で最近処理したオブ"
"ジェクトを表す一方、 C レベルの例外状態情報が存続するのは、渡された例外情報"
"を ``sys.exc_info()`` その他に転送するよう取り計らう Python のバイトコードイ"
"ンタプリタのメインループに到達するまで、例外が関数の間で受け渡しされている間"
"だけです。"
#: ../../c-api/intro.rst:629
msgid ""
"Note that starting with Python 1.5, the preferred, thread-safe way to access "
"the exception state from Python code is to call the function :func:`sys."
"exc_info`, which returns the per-thread exception state for Python code. "
"Also, the semantics of both ways to access the exception state have changed "
"so that a function which catches an exception will save and restore its "
"thread's exception state so as to preserve the exception state of its "
"caller. This prevents common bugs in exception handling code caused by an "
"innocent-looking function overwriting the exception being handled; it also "
"reduces the often unwanted lifetime extension for objects that are "
"referenced by the stack frames in the traceback."
msgstr ""
"Python 1.5 からは、Python で書かれたコードから例外状態情報にアクセスする方法"
"として、推奨されていてスレッドセーフな方法は :func:`sys.exc_info` になってい"
"るので注意してください。この関数は Python コードの実行されているスレッドにお"
"ける例外状態情報を返します。また、これらの例外状態情報に対するアクセス手段"
"は、両方とも意味づけ (semantics) が変更され、ある関数が例外を捕捉すると、その"
"関数を実行しているスレッドの例外状態情報を保存して、呼び出し側の例外状態情報"
"を維持するようになりました。この変更によって、無害そうに見える関数が現在扱っ"
"ている例外を上書きすることで引き起こされる、例外処理コードでよくおきていたバ"
"グを抑止しています; また、トレースバック内のスタックフレームで参照されている"
"オブジェクトがしばしば不必要に寿命を永らえていたのをなくしています。"
#: ../../c-api/intro.rst:640
msgid ""
"As a general principle, a function that calls another function to perform "
"some task should check whether the called function raised an exception, and "
"if so, pass the exception state on to its caller. It should discard any "
"object references that it owns, and return an error indicator, but it "
"should *not* set another exception --- that would overwrite the exception "
"that was just raised, and lose important information about the exact cause "
"of the error."
msgstr ""
"一般的な原理として、ある関数が別の関数を呼び出して何らかの作業をさせるとき、"
"呼び出し先の関数が例外を送出していないか調べなくてはならず、もし送出していれ"
"ば、その例外状態情報は呼び出し側に渡されなければなりません。呼び出し元の関数"
"はオブジェクト参照の所有権をすべて放棄し、エラー指標を返さなくてはなりません"
"が、余計に例外を設定する必要は *ありません* --- そんなことをすれば、たった今"
"送出されたばかりの例外を上書きしてしまい、エラーの原因そのものに関する重要な"
"情報を失うことになります。"
#: ../../c-api/intro.rst:649
msgid ""
"A simple example of detecting exceptions and passing them on is shown in "