exceptions.po

# 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:
# Akira inamori <akira.inamori@tf-ebina.com>, 2021
# Tetsuo Koyama <tkoyama010@gmail.com>, 2022
# Arihiro TAKASE, 2023
# Osamu NAKAMURA, 2023
# tomo, 2023
# Taichi Haradaguchi, 2024
# 石井明久, 2025
#
#,fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.13\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-04-25 14:19+0000\n"
"PO-Revision-Date: 2021-06-28 00:48+0000\n"
"Last-Translator: 石井明久, 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""
"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:322
msgid""
"Like :c:func:`PyErr_SyntaxLocationEx`, but the *col_offset* parameter is "
"omitted."
msgstr""
":c:func:`PyErr_SyntaxLocationEx` と似ていますが、 *col_offset* 引数が除去され"
"ています。"

#:../../c-api/exceptions.rst:328
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:335
msgid"Issuing warnings"
msgstr"警告"

#:../../c-api/exceptions.rst:337
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:352
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:359
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:365
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:372
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:383
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:390
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:399
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:406
msgid"Querying the error indicator"
msgstr"エラーインジケータの問い合わせ"

#:../../c-api/exceptions.rst:410
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:416
msgid"The caller must hold the GIL."
msgstr"呼び出し側はGILを獲得する必要があります"

#:../../c-api/exceptions.rst:420
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:428
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:435
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:443
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:446
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:449../../c-api/exceptions.rst:493
msgid"For example::"
msgstr"例えば::"

#:../../c-api/exceptions.rst:451
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:459
msgid""
":c:func:`PyErr_GetHandledException`, to save the exception currently being "
"handled."
msgstr""

#:../../c-api/exceptions.rst:467
msgid""
"Set *exc* as the exception currently being raised, clearing the existing "
"exception if one is set."
msgstr""

#:../../c-api/exceptions.rst:472
msgid"This call steals a reference to *exc*, which must be a valid exception."
msgstr""

#:../../c-api/exceptions.rst:481
msgid"Use :c:func:`PyErr_GetRaisedException` instead."
msgstr""

#:../../c-api/exceptions.rst:483
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:490
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:495
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:509
msgid"Use :c:func:`PyErr_SetRaisedException` instead."
msgstr""

#:../../c-api/exceptions.rst:511
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:525
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:534
msgid""
"Use :c:func:`PyErr_GetRaisedException` instead, to avoid any possible de-"
"normalization."
msgstr""

#:../../c-api/exceptions.rst:537
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:545
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:550
msgid""
"if (tb != NULL) {\n"
" PyException_SetTraceback(val, tb);\n"
"}"
msgstr""

#:../../c-api/exceptions.rst:557
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:564
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:573
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:580
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:589
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: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_SetExcInfo` to restore or clear the "
"exception state."
msgstr""
"この関数は、通常は例外を扱うコードでは使用されません。正確に言うと、これは例"
"外の状態を一時的に保存し、元に戻す必要があるコードで使用することができます。"
"例外の状態を元に戻す、もしくはクリアするには :c:func:`PyErr_SetExcInfo` を"
"使ってください。"

#:../../c-api/exceptions.rst:608
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:617
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:624
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:632
msgid"Signal Handling"
msgstr"シグナルハンドリング"

#:../../c-api/exceptions.rst:642
msgid"This function interacts with Python's signal handling."
msgstr""

#:../../c-api/exceptions.rst:644
msgid""
"If the function is called from the main thread and under the main Python "
"interpreter, it checks whether a signal has been sent to the processes and "
"if so, invokes the corresponding signal handler. If the :mod:`signal` "
"module is supported, this can invoke a signal handler written in Python."
msgstr""

#:../../c-api/exceptions.rst:649
msgid""
"The function attempts to handle all pending signals, and then returns ``0``. "
"However, if a Python signal handler raises an exception, the error indicator "
"is set and the function returns ``-1`` immediately (such that other pending "
"signals may not have been handled yet: they will be on the next :c:func:"
"`PyErr_CheckSignals()` invocation)."
msgstr""

#:../../c-api/exceptions.rst:655
msgid""
"If the function is called from a non-main thread, or under a non-main Python "
"interpreter, it does nothing and returns ``0``."
msgstr""

#:../../c-api/exceptions.rst:658
msgid""
"This function can be called by long-running C code that wants to be "
"interruptible by user requests (such as by pressing Ctrl-C)."
msgstr""

#:../../c-api/exceptions.rst:662
msgid""
"The default Python signal handler for :c:macro:`!SIGINT` raises the :exc:"
"`KeyboardInterrupt` exception."
msgstr""

#:../../c-api/exceptions.rst:673
msgid""
"Simulate the effect of a :c:macro:`!SIGINT` signal arriving. This is "
"equivalent to ``PyErr_SetInterruptEx(SIGINT)``."
msgstr""

#:../../c-api/exceptions.rst:677../../c-api/exceptions.rst:704
msgid""
"This function is async-signal-safe. It can be called without the :term:"
"`GIL` and from a C signal handler."
msgstr""

#:../../c-api/exceptions.rst:687
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:691
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:696
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:699
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:712
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""
"このユーティリティ関数は、シグナルを受け取ったときにシグナル番号をバイトとし"
"て書き込むファイル記述子を指定します。\n"
"*fd* はノンブロッキングでなければなりません。\n"
"この関数は、1つ前のファイル記述子を返します。"

#:../../c-api/exceptions.rst:716
msgid""
"The value ``-1`` disables the feature; this is the initial state. This is "
"equivalent to :func:`signal.set_wakeup_fd` in Python, but without any error "
"checking. *fd* should be a valid file descriptor. The function should only "
"be called from the main thread."
msgstr""
"値 ``-1`` を渡すと、この機能を無効にします; これが初期状態です。\n"
"この関数は Python の :func:`signal.set_wakeup_fd` と同等ですが、どんなエラー"
"チェックも行いません。\n"
"*fd* は有効なファイル記述子であるべきです。\n"
"この関数はメインスレッドからのみ呼び出されるべきです。"

#:../../c-api/exceptions.rst:721
msgid"On Windows, the function now also supports socket handles."
msgstr"Windowsで、この関数はソケットハンドルをサポートするようになりました。"

#:../../c-api/exceptions.rst:726
msgid"Exception Classes"
msgstr"例外クラス"

#:../../c-api/exceptions.rst:730
msgid""
"This utility function creates and returns a new exception class. The *name* "
"argument must be the name of the new exception, a C string of the form "
"``module.classname``. The *base* and *dict* arguments are normally "
"``NULL``. This creates a class object derived from :exc:`Exception` "
"(accessible in C as :c:data:`PyExc_Exception`)."
msgstr""
"このユーティリティ関数は新しい例外クラスを作成して返します。 *name* 引数は新"
"しい例外の名前、 ``module.classname`` 形式の C文字列でなければならない。 "
"*base* と *dict* 引数は通常 ``NULL`` です。これはすべての例外のためのルート、"
"組み込み名 :exc:`Exception` (Cでは :c:data:`PyExc_Exception` としてアクセス可"
"能)をルートとして派生したクラスオブジェクトを作成します。"

#:../../c-api/exceptions.rst:736
msgid""
"The :attr:`~type.__module__` attribute of the new class is set to the first "
"part (up to the last dot) of the *name* argument, and the class name is set "
"to the last part (after the last dot). The *base* argument can be used to "
"specify alternate base classes; it can either be only one class or a tuple "
"of classes. The *dict* argument can be used to specify a dictionary of class "
"variables and methods."
msgstr""

#:../../c-api/exceptions.rst:745
msgid""
"Same as :c:func:`PyErr_NewException`, except that the new exception class "
"can easily be given a docstring: If *doc* is non-``NULL``, it will be used "
"as the docstring for the exception class."
msgstr""
":c:func:`PyErr_NewException` とほぼ同じですが、新しい例外クラスに簡単に "
"docstring を設定できます。 *doc* が ``NULL`` で無い場合、それが例外クラスの "
"docstring になります。"

#:../../c-api/exceptions.rst:753