[po] auto sync

github-actions[bot] · github-actions[bot] · commit 00624da9fc4b · 2022-03-23T03:27:06.000Z
diff --git a/extending/extending.po b/extending/extending.po
@@ -9,7 +9,7 @@
 # eric R <trencyclopedia@gmail.com>, 2021
 # taotieren <admin@taotieren.com>, 2021
 # Harry Liu. <harry.python@gmail.com>, 2021
-# Freesand Leo <yuqinju@163.com>, 2021
+# Freesand Leo <yuqinju@163.com>, 2022
 # 
 #, fuzzy
 msgid ""
@@ -18,7 +18,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2021-06-29 12:56+0000\n"
 "PO-Revision-Date: 2021-06-28 00:51+0000\n"
-"Last-Translator: Freesand Leo <yuqinju@163.com>, 2021\n"
+"Last-Translator: Freesand Leo <yuqinju@163.com>, 2022\n"
 "Language-Team: Chinese (China) (https://www.transifex.com/python-doc/teams/5390/zh_CN/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -1099,8 +1099,8 @@ msgid ""
 "gives full owner responsibilities (the new owner must dispose of the "
 "reference properly, as well as the previous owner)."
 msgstr ""
-"借用可以变为拥有引用，通过调用 :c:func:`Py_INCREF` "
-"。这不会影响已经借出的拥有者的状态。这回创建一个新的拥有引用，并给予完全的拥有者责任(新的拥有者必须恰当的处置引用，就像之前的拥有者那样)。"
+"借用可以变为拥有引用，通过调用 :c:func:`Py_INCREF`。 这不会影响已经借出的拥有者的状态。 "
+"这会创建一个新的拥有引用，并给予完全的拥有者责任（新的拥有者必须恰当的处置引用，就像之前的拥有者那样）。"
 
 #: ../../extending/extending.rst:962
 msgid "Ownership Rules"
diff --git a/howto/clinic.po b/howto/clinic.po
@@ -11,6 +11,7 @@
 # df2dc1c92e792f7ae8417c51df43db8f_594d92a <0f49be28017426edb1db1a2ab6e67088_717605>, 2021
 # ppcfish <ppcfish@gmail.com>, 2021
 # Dai Xu <daixu61@hotmail.com>, 2022
+# Freesand Leo <yuqinju@163.com>, 2022
 # 
 #, fuzzy
 msgid ""
@@ -19,7 +20,7 @@ msgstr ""
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2021-06-29 12:56+0000\n"
 "PO-Revision-Date: 2021-06-28 00:52+0000\n"
-"Last-Translator: Dai Xu <daixu61@hotmail.com>, 2022\n"
+"Last-Translator: Freesand Leo <yuqinju@163.com>, 2022\n"
 "Language-Team: Chinese (China) (https://www.transifex.com/python-doc/teams/5390/zh_CN/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -417,18 +418,19 @@ msgstr "这些参数行的常规形式如下："
 
 #: ../../howto/clinic.rst:276
 msgid "If the parameter has a default value, add that after the converter:"
-msgstr "如果参数带有默认值，请加在转换器之后："
+msgstr "如果参数带有缺省值，请加在转换器之后："
 
 #: ../../howto/clinic.rst:283
 msgid ""
 "Argument Clinic's support for \"default values\" is quite sophisticated; "
 "please see :ref:`the section below on default values <default_values>` for "
 "more information."
 msgstr ""
+"Argument Clinic 对 “缺省值” 的支持方式相当复杂；更多信息请参见 :ref:`关于缺省值的部分 <default_values>` 。"
 
 #: ../../howto/clinic.rst:287
 msgid "Add a blank line below the parameters."
-msgstr ""
+msgstr "在参数行下面添加一个空行。"
 
 #: ../../howto/clinic.rst:289
 msgid ""
@@ -438,6 +440,8 @@ msgid ""
 "convenience syntax intended to make porting old code into Argument Clinic "
 "easier."
 msgstr ""
+" “转换器”是什么？它既确定了 C 语言要采用的变量类型，又确定了运行时将 Python 值转换成 C "
+"语言值的方法。现在需用到的是所谓“传统转换器”——快捷语法，旨在让旧代码更容易移植到 Argument Clinic。"
 
 #: ../../howto/clinic.rst:296
 msgid ""
@@ -448,57 +452,63 @@ msgid ""
 "parsing function what the type of the variable is and how to convert it.  "
 "For more on format units please see :ref:`arg-parsing`.)"
 msgstr ""
+"每个参数都要从``PyArg_Parse()`` 格式参数中复制其 “格式单元”，并以带引号字符串的形式指定其转换器。（“格式单元”是 "
+"``format`` 参数的1-3个字符的正式名称，用于让参数解析函数知晓该变量的类型及转换方法。关于格式单位的更多信息，请参阅 :ref:`arg-"
+"parsing` ）。"
 
 #: ../../howto/clinic.rst:305
 msgid ""
 "For multicharacter format units like ``z#``, use the entire two-or-three "
 "character string."
-msgstr ""
+msgstr "对于像 ``z#`` 这样的多字符格式单元，要使用2-3个字符组成的整个字符串。"
 
 #: ../../howto/clinic.rst:323
 msgid ""
 "If your function has ``|`` in the format string, meaning some parameters "
 "have default values, you can ignore it.  Argument Clinic infers which "
 "parameters are optional based on whether or not they have default values."
 msgstr ""
+"如果函数的格式字符串包含 ``|``，意味着有些参数带有缺省值，这可以忽略。Argument Clinic 根据参数是否有缺省值来推断哪些参数是可选的。"
 
 #: ../../howto/clinic.rst:328
 msgid ""
 "If your function has ``$`` in the format string, meaning it takes keyword-"
 "only arguments, specify ``*`` on a line by itself before the first keyword-"
 "only argument, indented the same as the parameter lines."
-msgstr ""
+msgstr "如果函数的格式字符串中包含 $，意味着只接受关键字参数，请在第一个关键字参数之前单独给出一行 ``*``，缩进与参数行对齐。"
 
 #: ../../howto/clinic.rst:333
 msgid "(``_pickle.Pickler.dump`` has neither, so our sample is unchanged.)"
-msgstr ""
+msgstr "（``_pickle.Pickler.dump`` 两种格式字符串都没有，所以这里的示例不用改动。）"
 
 #: ../../howto/clinic.rst:336
 msgid ""
 "If the existing C function calls :c:func:`PyArg_ParseTuple` (as opposed to "
 ":c:func:`PyArg_ParseTupleAndKeywords`), then all its arguments are "
 "positional-only."
 msgstr ""
+"如果 C 函数调用的是 :c:func:`PyArg_ParseTuple` (而不是 "
+":c:func:`PyArg_ParseTupleAndKeywords`)，那么其所有参数均是仅限位置参数。"
 
 #: ../../howto/clinic.rst:340
 msgid ""
 "To mark all parameters as positional-only in Argument Clinic, add a ``/`` on"
 " a line by itself after the last parameter, indented the same as the "
 "parameter lines."
-msgstr ""
+msgstr "若要在 Argument Clinic 中把所有参数都标记为只认位置，请在最后一个参数后面一行加入一个 ``/``，缩进程度与参数行对齐。"
 
 #: ../../howto/clinic.rst:344
 msgid ""
 "Currently this is all-or-nothing; either all parameters are positional-only,"
 " or none of them are.  (In the future Argument Clinic may relax this "
 "restriction.)"
-msgstr ""
+msgstr "目前这个标记是全体生效；要么所有参数都是只认位置，要么都不是。（以后 Argument Clinic 可能会放宽这一限制。）"
 
 #: ../../howto/clinic.rst:364
 msgid ""
 "It's helpful to write a per-parameter docstring for each parameter. But per-"
 "parameter docstrings are optional; you can skip this step if you prefer."
-msgstr ""
+msgstr "为每个参数都编写一个文档字符串，这很有意义。但这是可选项；可以跳过这一步。"
 
 #: ../../howto/clinic.rst:368
 msgid ""
@@ -509,33 +519,39 @@ msgid ""
 "this amount.  You can write as much text as you like, across multiple lines "
 "if you wish."
 msgstr ""
+"下面介绍如何添加逐参数的文档字符串。逐参数文档字符串的第一行必须比参数定义多缩进一层。第一行的左边距即确定了所有逐参数文档字符串的左边距；所有文档字符串文本都要同等缩进。文本可以用多行编写。"
 
 #: ../../howto/clinic.rst:392
 msgid ""
 "Save and close the file, then run ``Tools/clinic/clinic.py`` on it.  With "
 "luck everything worked---your block now has output, and a ``.c.h`` file has "
 "been generated! Reopen the file in your text editor to see::"
 msgstr ""
+"保存并关闭该文件，然后运行 ``Tools/clinic/clinic.py`` 。 运气好的话就万事大吉——程序块现在有了输出信息，并且生成了一个 "
+"``.c.h`` 文件！在文本编辑器中重新打开该文件，可以看到："
 
 #: ../../howto/clinic.rst:411
 msgid ""
 "Obviously, if Argument Clinic didn't produce any output, it's because it "
 "found an error in your input.  Keep fixing your errors and retrying until "
 "Argument Clinic processes your file without complaint."
 msgstr ""
+"显然，如果 Argument Clinic 未产生任何输出，那是因为在输入信息中发现了错误。继续修正错误并重试，直至 Argument Clinic "
+"正确地处理好文件。"
 
 #: ../../howto/clinic.rst:415
 msgid ""
 "For readability, most of the glue code has been generated to a ``.c.h`` "
 "file.  You'll need to include that in your original ``.c`` file, typically "
 "right after the clinic module block::"
 msgstr ""
+"为了便于阅读，大部分“胶水”代码已写入 ``.c.h`` 文件中。需在原 ``.c`` 文件中包含这个文件，通常是在 clinic  模块之后："
 
 #: ../../howto/clinic.rst:421
 msgid ""
 "Double-check that the argument-parsing code Argument Clinic generated looks "
 "basically the same as the existing code."
-msgstr ""
+msgstr "请仔细检查 Argument Clinic 生成的参数解析代码，是否与原有代码基本相同。"
 
 #: ../../howto/clinic.rst:424
 msgid ""
@@ -544,13 +560,18 @@ msgid ""
 ":c:func:`PyArg_ParseTupleAndKeywords`; ensure that the code generated by "
 "Argument Clinic calls the *exact* same function."
 msgstr ""
+"首先，确保两种代码使用相同的参数解析函数。原有代码必须调用  :c:func:`PyArg_ParseTuple` 或 "
+":c:func:`PyArg_ParseTupleAndKeywords` ；确保 Argument Clinic 生成的代码调用 *完全* "
+"相同的函数。"
 
 #: ../../howto/clinic.rst:430
 msgid ""
 "Second, the format string passed in to :c:func:`PyArg_ParseTuple` or "
 ":c:func:`PyArg_ParseTupleAndKeywords` should be *exactly* the same as the "
 "hand-written one in the existing function, up to the colon or semi-colon."
 msgstr ""
+"其次，传给 :c:func:`PyArg_ParseTuple` 或 :c:func:`PyArg_ParseTupleAndKeywords` "
+"的格式字符串应该 *完全* 与原有函数中的相同，直到冒号或分号为止。"
 
 #: ../../howto/clinic.rst:435
 msgid ""
diff --git a/library/unittest.po b/library/unittest.po
@@ -2389,7 +2389,7 @@ msgstr ":class:`TestLoader` 对象具有下列方法:"
 msgid ""
 "Return a suite of all test cases contained in the :class:`TestCase`\\ "
 "-derived :class:`testCaseClass`."
-msgstr ""
+msgstr "返回一个包含在 :class:`TestCase` 所派生的 :class:`testCaseClass` 中的所有测试用例的测试套件。"
 
 #: ../../library/unittest.rst:1756
 msgid ""
@@ -2399,13 +2399,18 @@ msgid ""
 ":meth:`runTest` method is implemented, a single test case is created for "
 "that method instead."
 msgstr ""
+"会为每个由 :meth:`getTestCaseNames` 指明的方法创建一个测试用例实例。 在默认情况下这些都是以 ``test`` "
+"开头的方法名称。 如果 :meth:`getTestCaseNames` 不返回任何方法，但 :meth:`runTest` "
+"方法已被实现，则会为该方法创建一个单独的测试用例。"
 
 #: ../../library/unittest.rst:1765
 msgid ""
 "Return a suite of all test cases contained in the given module. This method "
 "searches *module* for classes derived from :class:`TestCase` and creates an "
 "instance of the class for each test method defined for the class."
 msgstr ""
+"返回包含在给定模块中的所有测试用例的测试套件。 此方法会在 *module* 中搜索从派生自 :class:`TestCase` "
+"的类并为该类定义的每个测试方法创建一个类实例。"
 
 #: ../../library/unittest.rst:1772
 msgid ""
@@ -2415,6 +2420,9 @@ msgid ""
 "play well with this method.  Doing so, however, can be useful when the "
 "fixtures are different and defined in subclasses."
 msgstr ""
+"虽然使用 :class:`TestCase` "
+"所派生的类的层级结构可以方便地共享配置和辅助函数，但在不打算直接实例化的基类上定义测试方法并不能很好地配合此方法使用。 "
+"不过，当配置有差异并且定义在子类当中时这样做还是有用处的。"
 
 #: ../../library/unittest.rst:1778
 msgid ""
@@ -2423,6 +2431,8 @@ msgid ""
 "`load_tests protocol`_.  The *pattern* argument is passed as the third "
 "argument to ``load_tests``."
 msgstr ""
+"如果一个模块提供了 ``load_tests`` 函数则它将被调用以加载测试。 这允许模块自行定制测试加载过程。 这就称为 `load_tests "
+"protocol`_。 *pattern* 参数会被作为传给 ``load_tests`` 的第三个参数。"
 
 #: ../../library/unittest.rst:1783
 msgid "Support for ``load_tests`` added."
