# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001 Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR , 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-25 14:44+0000\n"
"PO-Revision-Date: 2025-09-16 00:02+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"
#: ../../reference/introduction.rst:6
msgid "Introduction"
msgstr "はじめに"
#: ../../reference/introduction.rst:8
msgid ""
"This reference manual describes the Python programming language. It is not "
"intended as a tutorial."
msgstr ""
"このリファレンスマニュアルは、Python プログラミング言語自体に関する記述です。"
"チュートリアルとして書かれたものではありません。"
#: ../../reference/introduction.rst:11
msgid ""
"While I am trying to be as precise as possible, I chose to use English "
"rather than formal specifications for everything except syntax and lexical "
"analysis. This should make the document more understandable to the average "
"reader, but will leave room for ambiguities. Consequently, if you were "
"coming from Mars and tried to re-implement Python from this document alone, "
"you might have to guess things and in fact you would probably end up "
"implementing quite a different language. On the other hand, if you are using "
"Python and wonder what the precise rules about a particular area of the "
"language are, you should definitely be able to find them here. If you would "
"like to see a more formal definition of the language, maybe you could "
"volunteer your time --- or invent a cloning machine :-)."
msgstr ""
"私は本マニュアルをできるだけ正確に書こうとする一方で、文法や字句解析以外の全"
"てについて、形式化された仕様記述ではなく英語を使うことにしました。そうするこ"
"とで、このドキュメントが平均的な読者にとってより読みやすくなっているはずです"
"が、ややあいまいな部分も残っていることでしょう。従って、もし読者のあなたが火"
"星から来ている人で、このドキュメントだけから Python を再度実装しようとしてい"
"るのなら、色々と推測しなければならないことがあり、実際にはおそらく全く別の言"
"語を実装する羽目になるでしょう。逆に、あなたが Python を利用しており、Python "
"言語のある特定の領域において、厳密な規則が何か疑問に思った場合、その答えはこ"
"のドキュメントで確実に見つけられることでしょう。もしより形式化された言語定義"
"をお望みなら、あなたの時間を提供していただいてかまいません --- もしくは、ク"
"ローン生成装置でも発明してください :-)。"
#: ../../reference/introduction.rst:23
msgid ""
"It is dangerous to add too many implementation details to a language "
"reference document --- the implementation may change, and other "
"implementations of the same language may work differently. On the other "
"hand, CPython is the one Python implementation in widespread use (although "
"alternate implementations continue to gain support), and its particular "
"quirks are sometimes worth being mentioned, especially where the "
"implementation imposes additional limitations. Therefore, you'll find short "
"\"implementation notes\" sprinkled throughout the text."
msgstr ""
"実装に関する詳細を言語リファレンスのドキュメントに載せすぎるのは危険なことで"
"す --- 実装は変更されるかもしれず、同じ言語でも異なる実装は異なった動作をする"
"かもしれないからです。一方、CPython が広く使われている一つの Python 実装 (別"
"の実装も支持され続けていますが) なので、特定のクセについては、特に実装によっ"
"て何らかの制限が加えられている場合には、触れておく価値があります。従って、こ"
"のテキスト全体にわたって短い \"実装に関する注釈 (imprementation notes)\" がち"
"りばめられています。"
#: ../../reference/introduction.rst:32
msgid ""
"Every Python implementation comes with a number of built-in and standard "
"modules. These are documented in :ref:`library-index`. A few built-in "
"modules are mentioned when they interact in a significant way with the "
"language definition."
msgstr ""
"Python 実装はいずれも、数々の組み込みモジュールと標準モジュールが付属します。"
"それらについては、 :ref:`library-index` でドキュメント化されています。いくつ"
"かの組み込みモジュールについては、言語定義と重要なかかわりをもっているときに"
"ついて触れています。"
#: ../../reference/introduction.rst:41
msgid "Alternate Implementations"
msgstr "別のPythonの実装"
#: ../../reference/introduction.rst:43
msgid ""
"Though there is one Python implementation which is by far the most popular, "
"there are some alternate implementations which are of particular interest to "
"different audiences."
msgstr ""
"Pythonの実装としては、群を抜いて有名な実装がひとつ存在しています。それ以外の"
"実装に関しても、特定のユーザ間で興味が持たれています。"
#: ../../reference/introduction.rst:47
msgid "Known implementations include:"
msgstr "よく知られている実装には以下のものがあります:"
#: ../../reference/introduction.rst:49
msgid "CPython"
msgstr "CPython"
#: ../../reference/introduction.rst:50
msgid ""
"This is the original and most-maintained implementation of Python, written "
"in C. New language features generally appear here first."
msgstr ""
"これは最も保守されている初代のPython実装で、C言語で書かれています。ほとんどの"
"場合、言語の新機能がいち早く実装されます。"
#: ../../reference/introduction.rst:53
msgid "Jython"
msgstr "Jython"
#: ../../reference/introduction.rst:54
msgid ""
"Python implemented in Java. This implementation can be used as a scripting "
"language for Java applications, or can be used to create applications using "
"the Java class libraries. It is also often used to create tests for Java "
"libraries. More information can be found at `the Jython website `_."
msgstr ""
"Javaで実装されたPythonです。この実装はJavaアプリケーションのためのスクリプト"
"言語として、もしくはJavaクラスライブラリを使ったアプリケーションを作成するた"
"めに使用することができます。また、Javaライブラリのテストを作成するためにもし"
"ばしば使用されています。さらなる情報については `the Jython website `_ を参照してください。"
#: ../../reference/introduction.rst:59
msgid "Python for .NET"
msgstr "Python for .NET"
#: ../../reference/introduction.rst:60
msgid ""
"This implementation actually uses the CPython implementation, but is a "
"managed .NET application and makes .NET libraries available. It was created "
"by Brian Lloyd. For more information, see the `Python for .NET home page "
"`_."
msgstr ""
"この実装は内部ではCPythonを使用していますが、 .NETアプリケーションによって管"
"理されているので、 .NETライブラリを参照することが可能です。この実装はBrian "
"Lloydによって作成されました。さらなる情報については、 `Python for .NET home "
"page `_ を参照してください。"
#: ../../reference/introduction.rst:65
msgid "IronPython"
msgstr "IronPython"
#: ../../reference/introduction.rst:66
msgid ""
"An alternate Python for .NET. Unlike Python.NET, this is a complete Python "
"implementation that generates IL, and compiles Python code directly to .NET "
"assemblies. It was created by Jim Hugunin, the original creator of Jython. "
"For more information, see `the IronPython website `_."
msgstr ""
".NETでPythonを使用するためのもう一つの実装です。Python.NETとは異なり、完全に"
"ILを生成することができるPythonの実装あり、直接Pythonコードを.NETアセンブリに"
"コンパイルします。これはJythonの初代の開発者であるJim Huguninによって作られま"
"した。さらなる情報については `the IronPython website `_ を参照してください。"
#: ../../reference/introduction.rst:71
msgid "PyPy"
msgstr "PyPy"
#: ../../reference/introduction.rst:72
msgid ""
"An implementation of Python written completely in Python. It supports "
"several advanced features not found in other implementations like stackless "
"support and a Just in Time compiler. One of the goals of the project is to "
"encourage experimentation with the language itself by making it easier to "
"modify the interpreter (since it is written in Python). Additional "
"information is available on `the PyPy project's home page `_."
msgstr ""
"完全にPythonで書かれたPythonの実装です。他の実装には見られない、スタックレス"
"のサポートや、実行時 (Just in Time) コンパイラなどの高度な機能をサポートして"
"います。このプロジェクトの一つの目的は、（Pythonで書かれていることによっ"
"て、）インタプリタを簡単に修正できるようにして、言語自体での実験を後押しする"
"ことです。さらなる情報は `the PyPy project's home page `_ "
"にあります。"
#: ../../reference/introduction.rst:79
msgid ""
"Each of these implementations varies in some way from the language as "
"documented in this manual, or introduces specific information beyond what's "
"covered in the standard Python documentation. Please refer to the "
"implementation-specific documentation to determine what else you need to "
"know about the specific implementation you're using."
msgstr ""
"これらの各実装はこのマニュアルで文書化された言語とは多少異なっている、もしく"
"は、標準のPythonドキュメントと何処が異なっているかを定めた情報が公開されてい"
"るでしょう。あなたが使用している実装上で、代替手段を使う必要があるかどうかを"
"判断するためには、各実装の仕様書を参照してください。"
#: ../../reference/introduction.rst:89
msgid "Notation"
msgstr "本マニュアルにおける表記法"
#: ../../reference/introduction.rst:93
msgid ""
"The descriptions of lexical analysis and syntax use a grammar notation that "
"is a mixture of `EBNF `_ and `PEG `_. For example:"
msgstr ""
#: ../../reference/introduction.rst:106
msgid ""
"In this example, the first line says that a ``name`` is a ``letter`` "
"followed by a sequence of zero or more ``letter``\\ s, ``digit``\\ s, and "
"underscores. A ``letter`` in turn is any of the single characters ``'a'`` "
"through ``'z'`` and ``A`` through ``Z``; a ``digit`` is a single character "
"from ``0`` to ``9``."
msgstr ""
#: ../../reference/introduction.rst:112
msgid ""
"Each rule begins with a name (which identifies the rule that's being "
"defined) followed by a colon, ``:``. The definition to the right of the "
"colon uses the following syntax elements:"
msgstr ""
#: ../../reference/introduction.rst:116
msgid ""
"``name``: A name refers to another rule. Where possible, it is a link to the "
"rule's definition."
msgstr ""
#: ../../reference/introduction.rst:119
msgid ""
"``TOKEN``: An uppercase name refers to a :term:`token`. For the purposes of "
"grammar definitions, tokens are the same as rules."
msgstr ""
#: ../../reference/introduction.rst:122
msgid ""
"``\"text\"``, ``'text'``: Text in single or double quotes must match "
"literally (without the quotes). The type of quote is chosen according to the "
"meaning of ``text``:"
msgstr ""
#: ../../reference/introduction.rst:126
msgid "``'if'``: A name in single quotes denotes a :ref:`keyword `."
msgstr ""
#: ../../reference/introduction.rst:127
msgid ""
"``\"case\"``: A name in double quotes denotes a :ref:`soft-keyword `."
msgstr ""
#: ../../reference/introduction.rst:129
msgid ""
"``'@'``: A non-letter symbol in single quotes denotes an :py:data:`~token."
"OP` token, that is, a :ref:`delimiter ` or :ref:`operator "
"`."
msgstr ""
#: ../../reference/introduction.rst:133
msgid ""
"``e1 e2``: Items separated only by whitespace denote a sequence. Here, "
"``e1`` must be followed by ``e2``."
msgstr ""
#: ../../reference/introduction.rst:135
msgid ""
"``e1 | e2``: A vertical bar is used to separate alternatives. It denotes "
"PEG's \"ordered choice\": if ``e1`` matches, ``e2`` is not considered. In "
"traditional PEG grammars, this is written as a slash, ``/``, rather than a "
"vertical bar. See :pep:`617` for more background and details."
msgstr ""
#: ../../reference/introduction.rst:141
msgid "``e*``: A star means zero or more repetitions of the preceding item."
msgstr ""
#: ../../reference/introduction.rst:142
msgid "``e+``: Likewise, a plus means one or more repetitions."
msgstr ""
#: ../../reference/introduction.rst:143
msgid ""
"``[e]``: A phrase enclosed in square brackets means zero or one occurrences. "
"In other words, the enclosed phrase is optional."
msgstr ""
#: ../../reference/introduction.rst:145
msgid ""
"``e?``: A question mark has exactly the same meaning as square brackets: the "
"preceding item is optional."
msgstr ""
#: ../../reference/introduction.rst:147
msgid "``(e)``: Parentheses are used for grouping."
msgstr ""
#: ../../reference/introduction.rst:149
msgid ""
"The following notation is only used in :ref:`lexical definitions `."
msgstr ""
#: ../../reference/introduction.rst:152
msgid ""
"``\"a\"...\"z\"``: Two literal characters separated by three dots mean a "
"choice of any single character in the given (inclusive) range of ASCII "
"characters."
msgstr ""
#: ../../reference/introduction.rst:154
msgid ""
"``<...>``: A phrase between angular brackets gives an informal description "
"of the matched symbol (for example, ````), or an abbreviation that is defined in nearby text (for example, "
"````)."
msgstr ""
#: ../../reference/introduction.rst:160
msgid ""
"Some definitions also use *lookaheads*, which indicate that an element must "
"(or must not) match at a given position, but without consuming any input:"
msgstr ""
#: ../../reference/introduction.rst:163
msgid "``&e``: a positive lookahead (that is, ``e`` is required to match)"
msgstr ""
#: ../../reference/introduction.rst:164
msgid ""
"``!e``: a negative lookahead (that is, ``e`` is required *not* to match)"
msgstr ""
#: ../../reference/introduction.rst:166
msgid ""
"The unary operators (``*``, ``+``, ``?``) bind as tightly as possible; the "
"vertical bar (``|``) binds most loosely."
msgstr ""
#: ../../reference/introduction.rst:169
msgid "White space is only meaningful to separate tokens."
msgstr ""
#: ../../reference/introduction.rst:171
msgid ""
"Rules are normally contained on a single line, but rules that are too long "
"may be wrapped:"
msgstr ""
#: ../../reference/introduction.rst:180
msgid ""
"Alternatively, rules may be formatted with the first line ending at the "
"colon, and each alternative beginning with a vertical bar on a new line. For "
"example:"
msgstr ""
#: ../../reference/introduction.rst:195
msgid "This does *not* mean that there is an empty first alternative."
msgstr ""
#: ../../reference/introduction.rst:202
msgid "Lexical and Syntactic definitions"
msgstr ""
#: ../../reference/introduction.rst:204
msgid ""
"There is some difference between *lexical* and *syntactic* analysis: the :"
"term:`lexical analyzer` operates on the individual characters of the input "
"source, while the *parser* (syntactic analyzer) operates on the stream of :"
"term:`tokens ` generated by the lexical analysis. However, in some "
"cases the exact boundary between the two phases is a CPython implementation "
"detail."
msgstr ""
#: ../../reference/introduction.rst:211
msgid ""
"The practical difference between the two is that in *lexical* definitions, "
"all whitespace is significant. The lexical analyzer :ref:`discards "
"` all whitespace that is not converted to tokens like :data:"
"`token.INDENT` or :data:`~token.NEWLINE`. *Syntactic* definitions then use "
"these tokens, rather than source characters."
msgstr ""
#: ../../reference/introduction.rst:217
msgid ""
"This documentation uses the same BNF grammar for both styles of definitions. "
"All uses of BNF in the next chapter (:ref:`lexical`) are lexical "
"definitions; uses in subsequent chapters are syntactic definitions."
msgstr ""
#: ../../reference/introduction.rst:91
msgid "BNF"
msgstr "BNF"
#: ../../reference/introduction.rst:91
msgid "grammar"
msgstr "文法"
#: ../../reference/introduction.rst:91
msgid "syntax"
msgstr "構文"
#: ../../reference/introduction.rst:91
msgid "notation"
msgstr "記法"
#: ../../reference/introduction.rst:197
msgid "lexical definitions"
msgstr "字句解析"