-
-
Notifications
You must be signed in to change notification settings - Fork 37
Expand file tree
/
Copy pathexceptions.po
More file actions
1830 lines (1561 loc) · 72.9 KB
/
exceptions.po
File metadata and controls
1830 lines (1561 loc) · 72.9 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
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.14\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-02-21 14:20+0000\n"
"PO-Revision-Date: 2025-09-16 00:00+0000\n"
"Last-Translator: python-doc bot, 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/exceptions.rst:8
msgid "Exception Handling"
msgstr "例外処理"
#: ../../c-api/exceptions.rst:10
msgid ""
"The functions described in this chapter will let you handle and raise Python "
"exceptions. It is important to understand some of the basics of Python "
"exception handling. It works somewhat like the POSIX :c:data:`errno` "
"variable: there is a global indicator (per thread) of the last error that "
"occurred. Most C API functions don't clear this on success, but will set it "
"to indicate the cause of the error on failure. Most C API functions also "
"return an error indicator, usually ``NULL`` if they are supposed to return a "
"pointer, or ``-1`` if they return an integer (exception: the ``PyArg_*`` "
"functions return ``1`` for success and ``0`` for failure)."
msgstr ""
"この章で説明する関数を使うと、 Python の例外の処理や例外の送出ができるように"
"なります。 Python の例外処理の基本をいくらか理解することが大切です。例外は "
"POSIX :c:data:`errno` 変数にやや似た機能を果たします: 発生した中で最も新しい"
"エラーの (スレッド毎の) グローバルなインジケータがあります。実行に成功した場"
"合にはほとんどの C API 関数がこれをクリアしませんが、失敗したときにはエラーの"
"原因を示すために設定します。ほとんどの C API 関数はエラーインジケータも返し、"
"通常は関数がポインタを返すことになっている場合は ``NULL`` であり、関数が整数"
"を返す場合は ``-1`` です。(例外: ``PyArg_*`` 関数は実行に成功したときに "
"``1`` を返し、失敗したときに ``0`` を返します)."
#: ../../c-api/exceptions.rst:20
msgid ""
"Concretely, the error indicator consists of three object pointers: the "
"exception's type, the exception's value, and the traceback object. Any of "
"those pointers can be ``NULL`` if non-set (although some combinations are "
"forbidden, for example you can't have a non-``NULL`` traceback if the "
"exception type is ``NULL``)."
msgstr ""
"具体的には、エラーインジケータは、例外の型、例外の値、トレースバックオブジェ"
"クトの３つのオブジェクトポインタで構成されます。これらのポインタはどれでも、"
"設定されない場合は ``NULL`` になりえます（ただし、いくつかの組み合わせは禁止"
"されており、例えば、例外の型が ``NULL`` の場合は、トレースバックは非 "
"``NULL`` の値になりません）"
#: ../../c-api/exceptions.rst:26
msgid ""
"When a function must fail because some function it called failed, it "
"generally doesn't set the error indicator; the function it called already "
"set it. It is responsible for either handling the error and clearing the "
"exception or returning after cleaning up any resources it holds (such as "
"object references or memory allocations); it should *not* continue normally "
"if it is not prepared to handle the error. If returning due to an error, it "
"is important to indicate to the caller that an error has been set. If the "
"error is not handled or carefully propagated, additional calls into the "
"Python/C API may not behave as intended and may fail in mysterious ways."
msgstr ""
"ある関数が呼び出した関数がいくつか失敗したために、その関数が失敗しなければな"
"らないとき、一般的にエラーインジケータを設定しません。呼び出した関数がすでに"
"設定しています。エラーを処理して例外をクリアするか、あるいは (オブジェクト参"
"照またはメモリ割り当てのような)それが持つどんなリソースも取り除いた後に戻るか"
"のどちらか一方を行う責任があります。エラーを処理する準備をしていなければ、普"
"通に続けるべきでは *ありません*。エラーのために戻る場合は、エラーが設定されて"
"いると呼び出し元に知らせることが大切です。エラーが処理されていない場合または"
"丁寧に伝えられている場合には、Python/C APIのさらなる呼び出しは意図した通りに"
"は動かない可能性があり、不可解な形で失敗するかもしれません。"
#: ../../c-api/exceptions.rst:37
msgid ""
"The error indicator is **not** the result of :func:`sys.exc_info`. The "
"former corresponds to an exception that is not yet caught (and is therefore "
"still propagating), while the latter returns an exception after it is caught "
"(and has therefore stopped propagating)."
msgstr ""
#: ../../c-api/exceptions.rst:44
msgid "Printing and clearing"
msgstr "出力とクリア"
#: ../../c-api/exceptions.rst:49
msgid ""
"Clear the error indicator. If the error indicator is not set, there is no "
"effect."
msgstr ""
"エラーインジケータをクリアします。エラーインジケータが設定されていないなら"
"ば、効果はありません。"
#: ../../c-api/exceptions.rst:55
msgid ""
"Print a standard traceback to ``sys.stderr`` and clear the error indicator. "
"**Unless** the error is a ``SystemExit``, in that case no traceback is "
"printed and the Python process will exit with the error code specified by "
"the ``SystemExit`` instance."
msgstr ""
"標準のトレースバックを ``sys.stderr`` に出力し、エラーインジケータをクリアし"
"ます。\n"
"ただし、エラーが ``SystemExit`` **である場合を除いて** です。\n"
"その場合、トレースバックは出力されず、 Python プロセスは ``SystemExit`` イン"
"スタンスで指定されたエラーコードで終了します。"
#: ../../c-api/exceptions.rst:60
msgid ""
"Call this function **only** when the error indicator is set. Otherwise it "
"will cause a fatal error!"
msgstr ""
"エラーインジケータが設定されているときに **だけ**、この関数を呼び出してくださ"
"い。\n"
"それ以外の場合、致命的なエラーを引き起こすでしょう!"
#: ../../c-api/exceptions.rst:63
msgid ""
"If *set_sys_last_vars* is nonzero, the variable :data:`sys.last_exc` is set "
"to the printed exception. For backwards compatibility, the deprecated "
"variables :data:`sys.last_type`, :data:`sys.last_value` and :data:`sys."
"last_traceback` are also set to the type, value and traceback of this "
"exception, respectively."
msgstr ""
#: ../../c-api/exceptions.rst:69
msgid "The setting of :data:`sys.last_exc` was added."
msgstr ""
#: ../../c-api/exceptions.rst:75
msgid "Alias for ``PyErr_PrintEx(1)``."
msgstr "``PyErr_PrintEx(1)`` のエイリアスです。"
#: ../../c-api/exceptions.rst:80
msgid ""
"Call :func:`sys.unraisablehook` using the current exception and *obj* "
"argument."
msgstr "現在の例外と *obj* 引数で :func:`sys.unraisablehook` を呼び出します。"
#: ../../c-api/exceptions.rst:83
msgid ""
"This utility function prints a warning message to ``sys.stderr`` when an "
"exception has been set but it is impossible for the interpreter to actually "
"raise the exception. It is used, for example, when an exception occurs in "
"an :meth:`~object.__del__` method."
msgstr ""
#: ../../c-api/exceptions.rst:88
msgid ""
"The function is called with a single argument *obj* that identifies the "
"context in which the unraisable exception occurred. If possible, the repr of "
"*obj* will be printed in the warning message. If *obj* is ``NULL``, only the "
"traceback is printed."
msgstr ""
#: ../../c-api/exceptions.rst:93
msgid "An exception must be set when calling this function."
msgstr "この関数を呼び出すときには、例外がセットされていなければなりません。"
#: ../../c-api/exceptions.rst:95
msgid "Print a traceback. Print only traceback if *obj* is ``NULL``."
msgstr ""
#: ../../c-api/exceptions.rst:98
msgid "Use :func:`sys.unraisablehook`."
msgstr ""
#: ../../c-api/exceptions.rst:104
msgid ""
"Similar to :c:func:`PyErr_WriteUnraisable`, but the *format* and subsequent "
"parameters help format the warning message; they have the same meaning and "
"values as in :c:func:`PyUnicode_FromFormat`. ``PyErr_WriteUnraisable(obj)`` "
"is roughly equivalent to ``PyErr_FormatUnraisable(\"Exception ignored in: "
"%R\", obj)``. If *format* is ``NULL``, only the traceback is printed."
msgstr ""
#: ../../c-api/exceptions.rst:116
msgid ""
"Print the standard traceback display of ``exc`` to ``sys.stderr``, including "
"chained exceptions and notes."
msgstr ""
#: ../../c-api/exceptions.rst:123
msgid "Raising exceptions"
msgstr "例外の送出"
#: ../../c-api/exceptions.rst:125
msgid ""
"These functions help you set the current thread's error indicator. For "
"convenience, some of these functions will always return a ``NULL`` pointer "
"for use in a ``return`` statement."
msgstr ""
"以下の関数は、現在のスレッドのエラーインジケータの設定を補助します。利便性の"
"ため、これらの関数のいくつかは、 ``return`` 文で利用できるように常に "
"``NULL`` ポインタを返します。"
#: ../../c-api/exceptions.rst:132
msgid ""
"This is the most common way to set the error indicator. The first argument "
"specifies the exception type; it is normally one of the standard exceptions, "
"e.g. :c:data:`PyExc_RuntimeError`. You need not create a new :term:`strong "
"reference` to it (e.g. with :c:func:`Py_INCREF`). The second argument is an "
"error message; it is decoded from ``'utf-8'``."
msgstr ""
#: ../../c-api/exceptions.rst:141
msgid ""
"This function is similar to :c:func:`PyErr_SetString` but lets you specify "
"an arbitrary Python object for the \"value\" of the exception."
msgstr ""
"この関数は :c:func:`PyErr_SetString` に似ていますが、例外の \"値(value)\" と"
"して任意のPythonオブジェクトを指定することができます。"
#: ../../c-api/exceptions.rst:147
msgid ""
"This function sets the error indicator and returns ``NULL``. *exception* "
"should be a Python exception class. The *format* and subsequent parameters "
"help format the error message; they have the same meaning and values as in :"
"c:func:`PyUnicode_FromFormat`. *format* is an ASCII-encoded string."
msgstr ""
"この関数はエラーインジケータを設定し ``NULL`` を返します。 *exception* は"
"Python例外クラスであるべきです。 *format* と以降の引数はエラーメッセージを作"
"るためのもので, :c:func:`PyUnicode_FromFormat` の引数と同じ意味を持っていま"
"す。 *format* は ASCII エンコードされた文字列です。"
#: ../../c-api/exceptions.rst:156
msgid ""
"Same as :c:func:`PyErr_Format`, but taking a :c:type:`va_list` argument "
"rather than a variable number of arguments."
msgstr ""
":c:func:`PyErr_Format` と同じですが、可変長引数の代わりに :c:type:`va_list` "
"引数を受け取ります。"
#: ../../c-api/exceptions.rst:164
msgid "This is a shorthand for ``PyErr_SetObject(type, Py_None)``."
msgstr "これは ``PyErr_SetObject(type, Py_None)`` を省略したものです。"
#: ../../c-api/exceptions.rst:169
msgid ""
"This is a shorthand for ``PyErr_SetString(PyExc_TypeError, message)``, where "
"*message* indicates that a built-in operation was invoked with an illegal "
"argument. It is mostly for internal use."
msgstr ""
"これは ``PyErr_SetString(PyExc_TypeError, message)`` を省略したもので、ここ"
"で *message* は組み込み操作が不正な引数で呼び出されたということを表していま"
"す。主に内部で使用するためのものです。"
#: ../../c-api/exceptions.rst:176
msgid ""
"This is a shorthand for ``PyErr_SetNone(PyExc_MemoryError)``; it returns "
"``NULL`` so an object allocation function can write ``return "
"PyErr_NoMemory();`` when it runs out of memory."
msgstr ""
"これは ``PyErr_SetNone(PyExc_MemoryError)`` を省略したもので、``NULL`` を返し"
"ます。したがって、メモリ不足になったとき、オブジェクト割り当て関数は "
"``return PyErr_NoMemory();`` と書くことができます。"
#: ../../c-api/exceptions.rst:185
msgid ""
"This is a convenience function to raise an exception when a C library "
"function has returned an error and set the C variable :c:data:`errno`. It "
"constructs a tuple object whose first item is the integer :c:data:`errno` "
"value and whose second item is the corresponding error message (gotten from :"
"c:func:`!strerror`), and then calls ``PyErr_SetObject(type, object)``. On "
"Unix, when the :c:data:`errno` value is :c:macro:`!EINTR`, indicating an "
"interrupted system call, this calls :c:func:`PyErr_CheckSignals`, and if "
"that set the error indicator, leaves it set to that. The function always "
"returns ``NULL``, so a wrapper function around a system call can write "
"``return PyErr_SetFromErrno(type);`` when the system call returns an error."
msgstr ""
#: ../../c-api/exceptions.rst:199
msgid ""
"Similar to :c:func:`PyErr_SetFromErrno`, with the additional behavior that "
"if *filenameObject* is not ``NULL``, it is passed to the constructor of "
"*type* as a third parameter. In the case of :exc:`OSError` exception, this "
"is used to define the :attr:`!filename` attribute of the exception instance."
msgstr ""
#: ../../c-api/exceptions.rst:208
msgid ""
"Similar to :c:func:`PyErr_SetFromErrnoWithFilenameObject`, but takes a "
"second filename object, for raising errors when a function that takes two "
"filenames fails."
msgstr ""
":c:func:`PyErr_SetFromErrnoWithFilenameObject` に似てますが、ファイル名を2つ"
"取る関数が失敗したときに例外を送出するために、2つ目のファイル名オブジェクトを"
"受け取ります。"
#: ../../c-api/exceptions.rst:217
msgid ""
"Similar to :c:func:`PyErr_SetFromErrnoWithFilenameObject`, but the filename "
"is given as a C string. *filename* is decoded from the :term:`filesystem "
"encoding and error handler`."
msgstr ""
":c:func:`PyErr_SetFromErrnoWithFilenameObject` に似ていますが、ファイル名は "
"C 文字列として与えられます。\n"
"*filename* は :term:`ファイルシステムのエンコーディングとエラーハンドラ "
"<filesystem encoding and error handler>` でデコードされます。"
#: ../../c-api/exceptions.rst:224
msgid ""
"This is a convenience function to raise :exc:`OSError`. If called with "
"*ierr* of ``0``, the error code returned by a call to :c:func:`!"
"GetLastError` is used instead. It calls the Win32 function :c:func:`!"
"FormatMessage` to retrieve the Windows description of error code given by "
"*ierr* or :c:func:`!GetLastError`, then it constructs a :exc:`OSError` "
"object with the :attr:`~OSError.winerror` attribute set to the error code, "
"the :attr:`~OSError.strerror` attribute set to the corresponding error "
"message (gotten from :c:func:`!FormatMessage`), and then calls "
"``PyErr_SetObject(PyExc_OSError, object)``. This function always returns "
"``NULL``."
msgstr ""
#: ../../c-api/exceptions.rst:234 ../../c-api/exceptions.rst:242
#: ../../c-api/exceptions.rst:253 ../../c-api/exceptions.rst:263
#: ../../c-api/exceptions.rst:271 ../../c-api/exceptions.rst:281
msgid "Availability"
msgstr ""
#: ../../c-api/exceptions.rst:239
msgid ""
"Similar to :c:func:`PyErr_SetFromWindowsErr`, with an additional parameter "
"specifying the exception type to be raised."
msgstr ""
":c:func:`PyErr_SetFromWindowsErr` に似ていますが、送出する例外の型を指定する"
"引数が追加されています。"
#: ../../c-api/exceptions.rst:247
msgid ""
"Similar to :c:func:`PyErr_SetFromWindowsErr`, with the additional behavior "
"that if *filename* is not ``NULL``, it is decoded from the filesystem "
"encoding (:func:`os.fsdecode`) and passed to the constructor of :exc:"
"`OSError` as a third parameter to be used to define the :attr:`!filename` "
"attribute of the exception instance."
msgstr ""
#: ../../c-api/exceptions.rst:258
msgid ""
"Similar to :c:func:`PyErr_SetExcFromWindowsErr`, with the additional "
"behavior that if *filename* is not ``NULL``, it is passed to the constructor "
"of :exc:`OSError` as a third parameter to be used to define the :attr:`!"
"filename` attribute of the exception instance."
msgstr ""
#: ../../c-api/exceptions.rst:268
msgid ""
"Similar to :c:func:`PyErr_SetExcFromWindowsErrWithFilenameObject`, but "
"accepts a second filename object."
msgstr ""
":c:func:`PyErr_SetExcFromWindowsErrWithFilenameObject` に似てますが、2つ目の"
"ファイル名オブジェクトを受け取ります。"
#: ../../c-api/exceptions.rst:278
msgid ""
"Similar to :c:func:`PyErr_SetFromWindowsErrWithFilename`, with an additional "
"parameter specifying the exception type to be raised."
msgstr ""
":c:func:`PyErr_SetFromWindowsErrWithFilename` に似ていますが、送出する例外の"
"型を指定する引数が追加されています。"
#: ../../c-api/exceptions.rst:286
msgid ""
"This is a convenience function to raise :exc:`ImportError`. *msg* will be "
"set as the exception's message string. *name* and *path*, both of which can "
"be ``NULL``, will be set as the :exc:`ImportError`'s respective ``name`` and "
"``path`` attributes."
msgstr ""
":exc:`ImportError` を簡単に送出するための関数です。 *msg* は例外のメッセージ"
"文字列としてセットされます。 *name* と *path* はどちらも ``NULL`` にしてよ"
"く、それぞれ :exc:`ImportError` の ``name`` 属性と ``path`` 属性としてセット"
"されます。"
#: ../../c-api/exceptions.rst:296
msgid ""
"Much like :c:func:`PyErr_SetImportError` but this function allows for "
"specifying a subclass of :exc:`ImportError` to raise."
msgstr ""
":c:func:`PyErr_SetImportError` とよく似ていますが、この関数は送出する例外とし"
"て、 :exc:`ImportError` のサブクラスを指定できます。"
#: ../../c-api/exceptions.rst:304
msgid ""
"Set file, line, and offset information for the current exception. If the "
"current exception is not a :exc:`SyntaxError`, then it sets additional "
"attributes, which make the exception printing subsystem think the exception "
"is a :exc:`SyntaxError`."
msgstr ""
"現在の例外のファイル、行、オフセットの情報をセットします。\n"
"現在の例外が :exc:`SyntaxError` でない場合は、例外を表示するサブシステムが、"
"例外が :exc:`SyntaxError` であると思えるように属性を追加します。"
#: ../../c-api/exceptions.rst:314
msgid ""
"Similar to :c:func:`PyErr_SyntaxLocationObject`, but also sets the "
"*end_lineno* and *end_col_offset* information for the current exception."
msgstr ""
#: ../../c-api/exceptions.rst:322
msgid ""
"Like :c:func:`PyErr_SyntaxLocationObject`, but *filename* is a byte string "
"decoded from the :term:`filesystem encoding and error handler`."
msgstr ""
":c:func:`PyErr_SyntaxLocationObject` と似ていますが、 *filename* は :term:`"
"ファイルシステムのエンコーディングとエラーハンドラ <filesystem encoding and "
"error handler>` でデコードされたバイト文字列です。"
#: ../../c-api/exceptions.rst:330
msgid ""
"Like :c:func:`PyErr_SyntaxLocationEx`, but the *col_offset* parameter is "
"omitted."
msgstr ""
":c:func:`PyErr_SyntaxLocationEx` と似ていますが、 *col_offset* 引数が除去され"
"ています。"
#: ../../c-api/exceptions.rst:336
msgid ""
"This is a shorthand for ``PyErr_SetString(PyExc_SystemError, message)``, "
"where *message* indicates that an internal operation (e.g. a Python/C API "
"function) was invoked with an illegal argument. It is mostly for internal "
"use."
msgstr ""
"``PyErr_SetString(PyExc_SystemError, message)`` を省略したものです。ここで "
"*message* は内部操作(例えば、Python/C API関数)が不正な引数とともに呼び出され"
"たということを示しています。主に内部で使用するためのものです。"
#: ../../c-api/exceptions.rst:344
msgid ""
"Get the source line in *filename* at line *lineno*. *filename* should be a "
"Python :class:`str` object."
msgstr ""
#: ../../c-api/exceptions.rst:347
msgid ""
"On success, this function returns a Python string object with the found "
"line. On failure, this function returns ``NULL`` without an exception set."
msgstr ""
#: ../../c-api/exceptions.rst:353
msgid ""
"Similar to :c:func:`PyErr_ProgramTextObject`, but *filename* is a :c:expr:"
"`const char *`, which is decoded with the :term:`filesystem encoding and "
"error handler`, instead of a Python object reference."
msgstr ""
#: ../../c-api/exceptions.rst:360
msgid "Issuing warnings"
msgstr "警告"
#: ../../c-api/exceptions.rst:362
msgid ""
"Use these functions to issue warnings from C code. They mirror similar "
"functions exported by the Python :mod:`warnings` module. They normally "
"print a warning message to *sys.stderr*; however, it is also possible that "
"the user has specified that warnings are to be turned into errors, and in "
"that case they will raise an exception. It is also possible that the "
"functions raise an exception because of a problem with the warning "
"machinery. The return value is ``0`` if no exception is raised, or ``-1`` if "
"an exception is raised. (It is not possible to determine whether a warning "
"message is actually printed, nor what the reason is for the exception; this "
"is intentional.) If an exception is raised, the caller should do its normal "
"exception handling (for example, :c:func:`Py_DECREF` owned references and "
"return an error value)."
msgstr ""
"以下の関数を使い、 C コードで起きた警告を報告します。\n"
"Python の :mod:`warnings` モジュールで公開されている同様の関数とよく似てま"
"す。\n"
"これらの関数は通常警告メッセージを *sys.stderr* へ出力しますが、ユーザが警告"
"をエラーへ変更するように指定することもでき、その場合は、関数は例外を送出しま"
"す。\n"
"警告機構がもつ問題のためにその関数が例外を送出するということも有り得ます。\n"
"例外が送出されない場合は戻り値は ``0`` で、例外が送出された場合は ``-1`` で"
"す。\n"
"(警告メッセージが実際に出力されるか、およびその例外の原因が何かについては判断"
"できません; これは意図的なものです。)\n"
"例外が送出された場合、呼び出し元は通常の例外処理を行います (例えば、保持して"
"いた参照に対し :c:func:`Py_DECREF` を行い、エラー値を返します)。"
#: ../../c-api/exceptions.rst:377
msgid ""
"Issue a warning message. The *category* argument is a warning category (see "
"below) or ``NULL``; the *message* argument is a UTF-8 encoded string. "
"*stack_level* is a positive number giving a number of stack frames; the "
"warning will be issued from the currently executing line of code in that "
"stack frame. A *stack_level* of 1 is the function calling :c:func:"
"`PyErr_WarnEx`, 2 is the function above that, and so forth."
msgstr ""
"警告メッセージを発行します。 *category* 引数は警告カテゴリ(以下を参照) かまた"
"は ``NULL`` で、 *message* 引数は UTF-8 エンコードされた文字列です。 "
"*stacklevel* はスタックフレームの数を示す正の整数です; 警告はそのスタックフ"
"レームの中の実行している行から発行されます。 *stacklevel* が 1 だと :c:func:"
"`PyErr_WarnEx` を呼び出している関数が、2 だとその上の関数が Warning の発行元"
"になります。"
#: ../../c-api/exceptions.rst:384
msgid ""
"Warning categories must be subclasses of :c:data:`PyExc_Warning`; :c:data:"
"`PyExc_Warning` is a subclass of :c:data:`PyExc_Exception`; the default "
"warning category is :c:data:`PyExc_RuntimeWarning`. The standard Python "
"warning categories are available as global variables whose names are "
"enumerated at :ref:`standardwarningcategories`."
msgstr ""
"警告カテゴリは :c:data:`PyExc_Warning` のサブクラスでなければなりません。 :c:"
"data:`PyExc_Warning` は :c:data:`PyExc_Exception` のサブクラスです。\n"
"デフォルトの警告カテゴリは :c:data:`PyExc_RuntimeWarning` です。\n"
"標準の Python 警告カテゴリは、 :ref:`standardwarningcategories` で名前が列挙"
"されているグローバル変数として利用可能です。"
#: ../../c-api/exceptions.rst:390
msgid ""
"For information about warning control, see the documentation for the :mod:"
"`warnings` module and the :option:`-W` option in the command line "
"documentation. There is no C API for warning control."
msgstr ""
"警告をコントロールするための情報については、 :mod:`warnings` モジュールのド"
"キュメンテーションとコマンドライン・ドキュメンテーションの :option:`-W` オプ"
"ションを参照してください。警告コントロールのためのC APIはありません。"
#: ../../c-api/exceptions.rst:397
msgid ""
"Issue a warning message with explicit control over all warning attributes. "
"This is a straightforward wrapper around the Python function :func:`warnings."
"warn_explicit`; see there for more information. The *module* and *registry* "
"arguments may be set to ``NULL`` to get the default effect described there."
msgstr ""
"すべての警告の属性を明示的に制御した警告メッセージを出します。これは Python "
"関数 :func:`warnings.warn_explicit` の直接的なラッパーで、さらに情報を得るに"
"はそちらを参照してください。そこに説明されているデフォルトの効果を得るため"
"に、 *module* と *registry* 引数は ``NULL`` に設定することができます。"
#: ../../c-api/exceptions.rst:408
msgid ""
"Similar to :c:func:`PyErr_WarnExplicitObject` except that *message* and "
"*module* are UTF-8 encoded strings, and *filename* is decoded from the :term:"
"`filesystem encoding and error handler`."
msgstr ""
":c:func:`PyErr_WarnExplicitObject` に似ていますが、 *message* と *module* が "
"UTF-8 エンコードされた文字列であるところが異なり、 *filename* は :term:`ファ"
"イルシステムのエンコーディングとエラーハンドラ <filesystem encoding and "
"error handler>` でデコードされます。"
#: ../../c-api/exceptions.rst:415
msgid ""
"Function similar to :c:func:`PyErr_WarnEx`, but use :c:func:"
"`PyUnicode_FromFormat` to format the warning message. *format* is an ASCII-"
"encoded string."
msgstr ""
":c:func:`PyErr_WarnEx` に似たような関数ですが、警告メッセージをフォーマットす"
"るのに :c:func:`PyUnicode_FromFormat` を使用します。 *format* は ASCII にエン"
"コードされた文字列です。"
#: ../../c-api/exceptions.rst:424
msgid ""
"Similar to :c:func:`PyErr_WarnExplicit`, but uses :c:func:"
"`PyUnicode_FromFormat` to format the warning message. *format* is an ASCII-"
"encoded string."
msgstr ""
#: ../../c-api/exceptions.rst:433
msgid ""
"Function similar to :c:func:`PyErr_WarnFormat`, but *category* is :exc:"
"`ResourceWarning` and it passes *source* to :class:`!warnings."
"WarningMessage`."
msgstr ""
#: ../../c-api/exceptions.rst:440
msgid "Querying the error indicator"
msgstr "エラーインジケータの問い合わせ"
#: ../../c-api/exceptions.rst:444
msgid ""
"Test whether the error indicator is set. If set, return the exception "
"*type* (the first argument to the last call to one of the ``PyErr_Set*`` "
"functions or to :c:func:`PyErr_Restore`). If not set, return ``NULL``. You "
"do not own a reference to the return value, so you do not need to :c:func:"
"`Py_DECREF` it."
msgstr ""
"エラーインジケータが設定されているかテストします。設定されている場合は、例外"
"の *型* (``PyErr_Set*`` 関数の一つあるいは :c:func:`PyErr_Restore` への最も新"
"しい呼び出しに対する第一引数)を返します。設定されていない場合は ``NULL`` を返"
"します。あなたは戻り値への参照を持っていませんので、それに :c:func:"
"`Py_DECREF` する必要はありません。"
#: ../../c-api/exceptions.rst:450
msgid "The caller must have an :term:`attached thread state`."
msgstr ""
#: ../../c-api/exceptions.rst:454
msgid ""
"Do not compare the return value to a specific exception; use :c:func:"
"`PyErr_ExceptionMatches` instead, shown below. (The comparison could easily "
"fail since the exception may be an instance instead of a class, in the case "
"of a class exception, or it may be a subclass of the expected exception.)"
msgstr ""
"戻り値を特定の例外と比較しないでください。その代わりに、下に示す :c:func:"
"`PyErr_ExceptionMatches` を使ってください。(比較は簡単に失敗するでしょう。な"
"ぜなら、例外はクラスではなくインスタンスかもしれないし、あるいは、クラス例外"
"の場合は期待される例外のサブクラスかもしれないからです。)"
#: ../../c-api/exceptions.rst:462
msgid ""
"Equivalent to ``PyErr_GivenExceptionMatches(PyErr_Occurred(), exc)``. This "
"should only be called when an exception is actually set; a memory access "
"violation will occur if no exception has been raised."
msgstr ""
"``PyErr_GivenExceptionMatches(PyErr_Occurred(), exc)`` と同じ。例外が実際に設"
"定されたときにだけ、これを呼び出だすべきです。例外が発生していないならば、メ"
"モリアクセス違反が起きるでしょう。"
#: ../../c-api/exceptions.rst:469
msgid ""
"Return true if the *given* exception matches the exception type in *exc*. "
"If *exc* is a class object, this also returns true when *given* is an "
"instance of a subclass. If *exc* is a tuple, all exception types in the "
"tuple (and recursively in subtuples) are searched for a match."
msgstr ""
"例外 *given* が *exc* の例外型と適合する場合に真を返します。\n"
"*exc* がクラスオブジェクトである場合も、 *given* がサブクラスのインスタンスで"
"あるときに真を返します。\n"
"*exc* がタプルの場合は、タプルにある (およびそのサブタプルに再帰的にある) す"
"べての例外型が適合するか調べられます。"
#: ../../c-api/exceptions.rst:477
msgid ""
"Return the exception currently being raised, clearing the error indicator at "
"the same time. Return ``NULL`` if the error indicator is not set."
msgstr ""
"現在発生している例外を返し、同時にエラーインジケータを消去します。エラーイン"
"ジケータが設定されていない場合は ``NULL`` を返します。"
#: ../../c-api/exceptions.rst:480
msgid ""
"This function is used by code that needs to catch exceptions, or code that "
"needs to save and restore the error indicator temporarily."
msgstr ""
"この関数は、例外をキャッチする必要があるコード、または一時的にエラーインジ"
"ケータを保存・復元する必要があるコードに使用されます。"
#: ../../c-api/exceptions.rst:483 ../../c-api/exceptions.rst:527
msgid "For example::"
msgstr "例えば::"
#: ../../c-api/exceptions.rst:485
msgid ""
"{\n"
" PyObject *exc = PyErr_GetRaisedException();\n"
"\n"
" /* ... code that might produce other errors ... */\n"
"\n"
" PyErr_SetRaisedException(exc);\n"
"}"
msgstr ""
"{\n"
" PyObject *exc = PyErr_GetRaisedException();\n"
"\n"
" /* ... 他のエラーを発生させる可能性があるコード ... */\n"
"\n"
" PyErr_SetRaisedException(exc);\n"
"}"
#: ../../c-api/exceptions.rst:493
msgid ""
":c:func:`PyErr_GetHandledException`, to save the exception currently being "
"handled."
msgstr ""
#: ../../c-api/exceptions.rst:501
msgid ""
"Set *exc* as the exception currently being raised, clearing the existing "
"exception if one is set."
msgstr ""
#: ../../c-api/exceptions.rst:506
msgid "This call steals a reference to *exc*, which must be a valid exception."
msgstr ""
#: ../../c-api/exceptions.rst:515
msgid "Use :c:func:`PyErr_GetRaisedException` instead."
msgstr ""
#: ../../c-api/exceptions.rst:517
msgid ""
"Retrieve the error indicator into three variables whose addresses are "
"passed. If the error indicator is not set, set all three variables to "
"``NULL``. If it is set, it will be cleared and you own a reference to each "
"object retrieved. The value and traceback object may be ``NULL`` even when "
"the type object is not."
msgstr ""
"エラーインジケータをアドレスを渡す三つの変数の中へ取り出します。エラーインジ"
"ケータが設定されていない場合は、三つすべての変数を ``NULL`` に設定します。エ"
"ラーインジケータが設定されている場合はクリアされ、あなたは取り出されたそれぞ"
"れのオブジェクトへの参照を持つことになります。型オブジェクトが ``NULL`` でな"
"いときでさえ、その値とトレースバックオブジェクトは ``NULL`` かもしれません。"
#: ../../c-api/exceptions.rst:524
msgid ""
"This function is normally only used by legacy code that needs to catch "
"exceptions or save and restore the error indicator temporarily."
msgstr ""
#: ../../c-api/exceptions.rst:529
msgid ""
"{\n"
" PyObject *type, *value, *traceback;\n"
" PyErr_Fetch(&type, &value, &traceback);\n"
"\n"
" /* ... code that might produce other errors ... */\n"
"\n"
" PyErr_Restore(type, value, traceback);\n"
"}"
msgstr ""
#: ../../c-api/exceptions.rst:543
msgid "Use :c:func:`PyErr_SetRaisedException` instead."
msgstr ""
#: ../../c-api/exceptions.rst:545
msgid ""
"Set the error indicator from the three objects, *type*, *value*, and "
"*traceback*, clearing the existing exception if one is set. If the objects "
"are ``NULL``, the error indicator is cleared. Do not pass a ``NULL`` type "
"and non-``NULL`` value or traceback. The exception type should be a class. "
"Do not pass an invalid exception type or value. (Violating these rules will "
"cause subtle problems later.) This call takes away a reference to each "
"object: you must own a reference to each object before the call and after "
"the call you no longer own these references. (If you don't understand this, "
"don't use this function. I warned you.)"
msgstr ""
#: ../../c-api/exceptions.rst:559
msgid ""
"This function is normally only used by legacy code that needs to save and "
"restore the error indicator temporarily. Use :c:func:`PyErr_Fetch` to save "
"the current error indicator."
msgstr ""
#: ../../c-api/exceptions.rst:568
msgid ""
"Use :c:func:`PyErr_GetRaisedException` instead, to avoid any possible de-"
"normalization."
msgstr ""
#: ../../c-api/exceptions.rst:571
msgid ""
"Under certain circumstances, the values returned by :c:func:`PyErr_Fetch` "
"below can be \"unnormalized\", meaning that ``*exc`` is a class object but "
"``*val`` is not an instance of the same class. This function can be used "
"to instantiate the class in that case. If the values are already "
"normalized, nothing happens. The delayed normalization is implemented to "
"improve performance."
msgstr ""
"ある状況では、以下の :c:func:`PyErr_Fetch` が返す値は \"正規化されていない\" "
"可能性があります。つまり、 ``*exc`` はクラスオブジェクトだが ``*val`` は同じ"
"クラスのインスタンスではないという意味です。この関数はそのような場合にそのク"
"ラスをインスタンス化するために使われます。その値がすでに正規化されている場合"
"は何も起きません。遅延正規化はパフォーマンスを改善するために実装されていま"
"す。"
#: ../../c-api/exceptions.rst:579
msgid ""
"This function *does not* implicitly set the :attr:`~BaseException."
"__traceback__` attribute on the exception value. If setting the traceback "
"appropriately is desired, the following additional snippet is needed::"
msgstr ""
#: ../../c-api/exceptions.rst:584
msgid ""
"if (tb != NULL) {\n"
" PyException_SetTraceback(val, tb);\n"
"}"
msgstr ""
#: ../../c-api/exceptions.rst:591
msgid ""
"Retrieve the active exception instance, as would be returned by :func:`sys."
"exception`. This refers to an exception that was *already caught*, not to an "
"exception that was freshly raised. Returns a new reference to the exception "
"or ``NULL``. Does not modify the interpreter's exception state."
msgstr ""
#: ../../c-api/exceptions.rst:598
msgid ""
"This function is not normally used by code that wants to handle exceptions. "
"Rather, it can be used when code needs to save and restore the exception "
"state temporarily. Use :c:func:`PyErr_SetHandledException` to restore or "
"clear the exception state."
msgstr ""
"この関数は、通常は例外を扱うコードでは使用されません。正確に言うと、これは例"
"外の状態を一時的に保存し、元に戻す必要があるコードで使用することができます。"
"例外の状態を元に戻す、もしくはクリアするには :c:func:"
"`PyErr_SetHandledException` を使ってください。"
#: ../../c-api/exceptions.rst:607
msgid ""
"Set the active exception, as known from ``sys.exception()``. This refers to "
"an exception that was *already caught*, not to an exception that was freshly "
"raised. To clear the exception state, pass ``NULL``."
msgstr ""
#: ../../c-api/exceptions.rst:614
msgid ""
"This function is not normally used by code that wants to handle exceptions. "
"Rather, it can be used when code needs to save and restore the exception "
"state temporarily. Use :c:func:`PyErr_GetHandledException` to get the "
"exception state."
msgstr ""
"この関数は、通常は例外を扱うコードでは使用されません。正確に言うと、これは例"
"外の状態を一時的に保存し、元に戻す必要があるコードで使用することができます。"
"例外の状態を取得するには :c:func:`PyErr_GetHandledException` を使ってくださ"
"い。"
#: ../../c-api/exceptions.rst:623
msgid ""
"Retrieve the old-style representation of the exception info, as known from :"
"func:`sys.exc_info`. This refers to an exception that was *already caught*, "
"not to an exception that was freshly raised. Returns new references for the "
"three objects, any of which may be ``NULL``. Does not modify the exception "
"info state. This function is kept for backwards compatibility. Prefer "
"using :c:func:`PyErr_GetHandledException`."
msgstr ""
#: ../../c-api/exceptions.rst:632
msgid ""
"This function is not normally used by code that wants to handle exceptions. "
"Rather, it can be used when code needs to save and restore the exception "
"state temporarily. Use :c:func:`PyErr_SetExcInfo` to restore or clear the "
"exception state."
msgstr ""
"この関数は、通常は例外を扱うコードでは使用されません。正確に言うと、これは例"
"外の状態を一時的に保存し、元に戻す必要があるコードで使用することができます。"
"例外の状態を元に戻す、もしくはクリアするには :c:func:`PyErr_SetExcInfo` を"
"使ってください。"
#: ../../c-api/exceptions.rst:642
msgid ""
"Set the exception info, as known from ``sys.exc_info()``. This refers to an "
"exception that was *already caught*, not to an exception that was freshly "
"raised. This function steals the references of the arguments. To clear the "
"exception state, pass ``NULL`` for all three arguments. This function is "
"kept for backwards compatibility. Prefer using :c:func:"
"`PyErr_SetHandledException`."
msgstr ""
#: ../../c-api/exceptions.rst:651
msgid ""
"This function is not normally used by code that wants to handle exceptions. "
"Rather, it can be used when code needs to save and restore the exception "
"state temporarily. Use :c:func:`PyErr_GetExcInfo` to read the exception "
"state."
msgstr ""
"この関数は、通常は例外を扱うコードでは使用されません。正確に言うと、これは例"
"外の状態を一時的に保存し、元に戻す必要があるコードで使用することができます。"
"例外の状態を取得するには :c:func:`PyErr_GetExcInfo` を使ってください。"
#: ../../c-api/exceptions.rst:658
msgid ""
"The ``type`` and ``traceback`` arguments are no longer used and can be NULL. "
"The interpreter now derives them from the exception instance (the ``value`` "
"argument). The function still steals references of all three arguments."
msgstr ""
#: ../../c-api/exceptions.rst:666
msgid "Signal Handling"
msgstr "シグナルハンドリング"
#: ../../c-api/exceptions.rst:676
msgid ""
"Handle external interruptions, such as signals or activating a debugger, "
"whose processing has been delayed until it is safe to run Python code and/or "
"raise exceptions."
msgstr ""
#: ../../c-api/exceptions.rst:680
msgid ""
"For example, pressing :kbd:`Ctrl-C` causes a terminal to send the :py:data:"
"`signal.SIGINT` signal. This function executes the corresponding Python "
"signal handler, which, by default, raises the :exc:`KeyboardInterrupt` "
"exception."
msgstr ""
#: ../../c-api/exceptions.rst:685
msgid ""
":c:func:`!PyErr_CheckSignals` should be called by long-running C code "
"frequently enough so that the response appears immediate to humans."
msgstr ""
#: ../../c-api/exceptions.rst:688
msgid "Handlers invoked by this function currently include:"
msgstr ""
#: ../../c-api/exceptions.rst:690
msgid ""
"Signal handlers, including Python functions registered using the :mod:"
"`signal` module."
msgstr ""
#: ../../c-api/exceptions.rst:693
msgid ""
"Signal handlers are only run in the main thread of the main interpreter."
msgstr ""
#: ../../c-api/exceptions.rst:695
msgid ""
"(This is where the function got the name: originally, signals were the only "
"way to interrupt the interpreter.)"
msgstr ""
#: ../../c-api/exceptions.rst:698
msgid "Running the garbage collector, if necessary."
msgstr ""
#: ../../c-api/exceptions.rst:700
msgid "Executing a pending :ref:`remote debugger <remote-debugging>` script."
msgstr ""
#: ../../c-api/exceptions.rst:702
msgid ""
"If any handler raises an exception, immediately return ``-1`` with that "
"exception set. Any remaining interruptions are left to be processed on the "
"next :c:func:`PyErr_CheckSignals()` invocation, if appropriate."
msgstr ""
#: ../../c-api/exceptions.rst:707
msgid ""
"If all handlers finish successfully, or there are no handlers to run, return "
"``0``."
msgstr ""
#: ../../c-api/exceptions.rst:710
msgid "This function may now invoke the garbage collector."
msgstr ""
#: ../../c-api/exceptions.rst:713
msgid ""
"This function may now execute a remote debugger script, if remote debugging "
"is enabled."
msgstr ""
#: ../../c-api/exceptions.rst:725
msgid ""
"Simulate the effect of a :c:macro:`!SIGINT` signal arriving. This is "
"equivalent to ``PyErr_SetInterruptEx(SIGINT)``."
msgstr ""
#: ../../c-api/exceptions.rst:729 ../../c-api/exceptions.rst:756
msgid ""
"This function is async-signal-safe. It can be called without an :term:"
"`attached thread state` and from a C signal handler."
msgstr ""
#: ../../c-api/exceptions.rst:739
msgid ""
"Simulate the effect of a signal arriving. The next time :c:func:"
"`PyErr_CheckSignals` is called, the Python signal handler for the given "
"signal number will be called."
msgstr ""
"シグナルが到達した効果をシミュレートします。\n"
"次に :c:func:`PyErr_CheckSignals` が呼ばれたとき、与えられたシグナル番号用の "
"Python のシグナルハンドラが呼び出されます。"
#: ../../c-api/exceptions.rst:743
msgid ""
"This function can be called by C code that sets up its own signal handling "
"and wants Python signal handlers to be invoked as expected when an "
"interruption is requested (for example when the user presses Ctrl-C to "
"interrupt an operation)."
msgstr ""
#: ../../c-api/exceptions.rst:748
msgid ""
"If the given signal isn't handled by Python (it was set to :py:const:`signal."
"SIG_DFL` or :py:const:`signal.SIG_IGN`), it will be ignored."
msgstr ""
#: ../../c-api/exceptions.rst:751
msgid ""
"If *signum* is outside of the allowed range of signal numbers, ``-1`` is "
"returned. Otherwise, ``0`` is returned. The error indicator is never "
"changed by this function."
msgstr ""
#: ../../c-api/exceptions.rst:764
msgid ""
"This utility function specifies a file descriptor to which the signal number "
"is written as a single byte whenever a signal is received. *fd* must be non-"
"blocking. It returns the previous such file descriptor."
msgstr ""
"このユーティリティ関数は、シグナルを受け取ったときにシグナル番号をバイトとし"