Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 2c85401

Browse files
github-actions[bot]github-actions[bot]
committed
[po] auto sync
1 parent 1c4d29b commit 2c85401

45 files changed

Lines changed: 246 additions & 248 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎distutils/apiref.po‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -157,8 +157,8 @@ msgstr "*maintainer*"
157157
#: ../../distutils/apiref.rst:61
158158
msgid ""
159159
"The name of the current maintainer, if different from the author. Note that "
160-
"if the maintainer is provided, distutils will use it as the author in "
161-
":file:`PKG-INFO`"
160+
"if the maintainer is provided, distutils will use it as the author in :file"
161+
":`PKG-INFO`"
162162
msgstr ""
163163

164164
#: ../../distutils/apiref.rst:68

‎distutils/builtdist.po‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -620,8 +620,8 @@ msgstr ""
620620

621621
#: ../../distutils/builtdist.rst:274
622622
msgid ""
623-
"If you wish, you can separate these three steps. You can use the :option:`!"
624-
"--spec-only` option to make :command:`bdist_rpm` just create the "
623+
"If you wish, you can separate these three steps. You can use the :option"
624+
":`!--spec-only` option to make :command:`bdist_rpm` just create the "
625625
":file:`.spec` file and exit; in this case, the :file:`.spec` file will be "
626626
"written to the \"distribution directory\"---normally :file:`dist/`, but "
627627
"customizable with the :option:`!--dist-dir` option. (Normally, the "

‎distutils/introduction.po‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -44,8 +44,8 @@ msgstr ""
4444
msgid ""
4545
"This document covers using the Distutils to distribute your Python modules, "
4646
"concentrating on the role of developer/distributor: if you're looking for "
47-
"information on installing Python modules, you should refer to the :ref"
48-
":`install-index` chapter."
47+
"information on installing Python modules, you should refer to the "
48+
":ref:`install-index` chapter."
4949
msgstr ""
5050
"本文档介绍了使用 Distutils 模块分发你的 Python 模块，主要是针对开发者/分发者的使用的——如果你想了解如何安装 Python "
5151
"模块，你应该参考这个章节： :ref:`install-index`。"

‎distutils/packageindex.po‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,6 @@ msgstr "`Python 包索引 (PyPI)`_ 存储描述与 distutils 和其他发布工
3434

3535
#: ../../distutils/packageindex.rst:13
3636
msgid ""
37-
"References to up to date PyPI documentation can be found at "
38-
":ref:`publishing-python-packages`."
37+
"References to up to date PyPI documentation can be found at :ref"
38+
":`publishing-python-packages`."
3939
msgstr "供参考的最新 PyPI 文档可以在 :ref:`publishing-python-packages` 找到。"

‎distutils/uploading.po‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,6 @@ msgstr "上传包到包索引"
2828

2929
#: ../../distutils/uploading.rst:7
3030
msgid ""
31-
"References to up to date PyPI documentation can be found at "
32-
":ref:`publishing-python-packages`."
31+
"References to up to date PyPI documentation can be found at :ref"
32+
":`publishing-python-packages`."
3333
msgstr "供参考的最新 PyPI 文档可以在 :ref:`publishing-python-packages` 找到。"

‎faq/design.po‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -443,9 +443,9 @@ msgstr ""
443443

444444
#: ../../faq/design.rst:303
445445
msgid ""
446-
"Answer 2: Fortunately, there is `Stackless Python "
447-
"<https://github.com/stackless-dev/stackless/wiki>`_, which has a completely "
448-
"redesigned interpreter loop that avoids the C stack."
446+
"Answer 2: Fortunately, there is `Stackless Python <https://github.com"
447+
"/stackless-dev/stackless/wiki>`_, which has a completely redesigned "
448+
"interpreter loop that avoids the C stack."
449449
msgstr ""
450450
"答案2： 幸运的是， `Stackless Python <https://github.com/stackless-"
451451
"dev/stackless/wiki>`_ 有一个完全重新设计的解释器循环，可以避免C堆栈。"
@@ -521,8 +521,8 @@ msgid ""
521521
"reference counting implementation."
522522
msgstr ""
523523
"但是，其他实现(如 `Jython <http://www.jython.org>`_ 或 `PyPy "
524-
"<http://www.pypy.org>`_ "
525-
")，)可以依赖不同的机制，如完全的垃圾回收器 。如果你的Python代码依赖于引用计数实现的行为，则这种差异可能会导致一些微妙的移植问题。"
524+
"<http://www.pypy.org>`_ )，)可以依赖不同的机制，如完全的垃圾回收器 "
525+
"。如果你的Python代码依赖于引用计数实现的行为，则这种差异可能会导致一些微妙的移植问题。"
526526

527527
#: ../../faq/design.rst:350
528528
msgid ""
@@ -960,8 +960,8 @@ msgid ""
960960
" pass on the string quote character by escaping it with a backslash. These "
961961
"rules work well when r-strings are used for their intended purpose."
962962
msgstr ""
963-
"原始字符串的设计是为了方便想要执行自己的反斜杠转义处理的处理器(主要是正则表达式引擎)创建输入。此类处理器将不匹配的尾随反斜杠视为错误，因此原始字符串不允许这样做。反过来，允许通过使用引号字符转义反斜杠转义字符串。当r-"
964-
"string用于它们的预期目的时，这些规则工作的很好。"
963+
"原始字符串的设计是为了方便想要执行自己的反斜杠转义处理的处理器(主要是正则表达式引擎)创建输入。此类处理器将不匹配的尾随反斜杠视为错误，因此原始字符串不允许这样做。反过来，允许通过使用引号字符转义反斜杠转义字符串"
964+
"。当r-string用于它们的预期目的时，这些规则工作的很好。"
965965

966966
#: ../../faq/design.rst:643
967967
msgid ""

‎faq/library.po‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -292,12 +292,12 @@ msgstr "怎样用 docstring 创建文档？"
292292
msgid ""
293293
"The :mod:`pydoc` module can create HTML from the doc strings in your Python "
294294
"source code. An alternative for creating API documentation purely from "
295-
"docstrings is `epydoc <http://epydoc.sourceforge.net/>`_. `Sphinx <http"
296-
"://sphinx-doc.org>`_ can also include docstring content."
295+
"docstrings is `epydoc <http://epydoc.sourceforge.net/>`_. `Sphinx "
296+
"<http://sphinx-doc.org>`_ can also include docstring content."
297297
msgstr ""
298298
":mod:`pydoc` 模块可以用 Python 源码中的 docstring 创建 HTML 文件。也可以使用 `epydoc "
299-
"<http://epydoc.sourceforge.net/>`_ 来只通过 docstring 创建 API 文档。`Sphinx <http"
300-
"://sphinx-doc.org>`_ 也可以引入 docstring 的内容。"
299+
"<http://epydoc.sourceforge.net/>`_ 来只通过 docstring 创建 API 文档。`Sphinx "
300+
"<http://sphinx-doc.org>`_ 也可以引入 docstring 的内容。"
301301

302302
#: ../../faq/library.rst:191
303303
msgid "How do I get a single keypress at a time?"

‎howto/logging-cookbook.po‎

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -252,8 +252,8 @@ msgid ""
252252
"handler classes, which would eat up one thread per handler for no particular"
253253
" benefit."
254254
msgstr ""
255-
"使用一个单独的类 "
256-
":class:`QueueListener` 优点是可以使用同一个实例去服务于多个``QueueHandlers``。这样会更节省资源，否则每个处理程序都占用一个线程没有任何益处。"
255+
"使用一个单独的类 :class:`QueueListener` "
256+
"优点是可以使用同一个实例去服务于多个``QueueHandlers``。这样会更节省资源，否则每个处理程序都占用一个线程没有任何益处。"
257257

258258
#: ../../howto/logging-cookbook.rst:370
259259
msgid "An example of using these two classes follows (imports omitted)::"
@@ -949,9 +949,8 @@ msgstr ""
949949
#: ../../howto/logging-cookbook.rst:1426
950950
msgid ""
951951
"For more information about this configuration, you can see the `relevant "
952-
"section "
953-
"<https://docs.djangoproject.com/en/stable/topics/logging/#configuring-"
954-
"logging>`_ of the Django documentation."
952+
"section <https://docs.djangoproject.com/en/stable/topics/logging"
953+
"/#configuring-logging>`_ of the Django documentation."
955954
msgstr ""
956955
"有关本配置的更多信息，请参阅 Django 文档的 `有关章节 "
957956
"<https://docs.djangoproject.com/en/stable/topics/logging/#configuring-"
@@ -1303,9 +1302,9 @@ msgstr "自定义信息对象的使用"
13031302
#: ../../howto/logging-cookbook.rst:2013
13041303
msgid ""
13051304
"There is another, perhaps simpler way that you can use {}- and $- formatting"
1306-
" to construct your individual log messages. You may recall (from "
1307-
":ref:`arbitrary-object-messages`) that when logging you can use an arbitrary"
1308-
" object as a message format string, and that the logging package will call "
1305+
" to construct your individual log messages. You may recall (from :ref"
1306+
":`arbitrary-object-messages`) that when logging you can use an arbitrary "
1307+
"object as a message format string, and that the logging package will call "
13091308
":func:`str` on that object to get the actual format string. Consider the "
13101309
"following two classes::"
13111310
msgstr ""
@@ -1412,8 +1411,8 @@ msgid ""
14121411
"configuration, and see the other cookbook recipe :ref:`custom-handlers` "
14131412
"above."
14141413
msgstr ""
1415-
"与过滤器一样，上述技术还可用于配置自定义 handler 和格式化对象。有关如何在日志配置中使用用户自定义对象的更多信息，请参阅 "
1416-
":ref:`logging-config-dict-userdef`，以及上述 :ref:`custom-handlers` 的其他指南。 "
1414+
"与过滤器一样，上述技术还可用于配置自定义 handler 和格式化对象。有关如何在日志配置中使用用户自定义对象的更多信息，请参阅 :ref"
1415+
":`logging-config-dict-userdef`，以及上述 :ref:`custom-handlers` 的其他指南。 "
14171416

14181417
#: ../../howto/logging-cookbook.rst:2164
14191418
msgid "Customized exception formatting"

‎library/array.po‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -241,8 +241,8 @@ msgid ""
241241
"the optional *initializer* value, which must be a list, a :term:`bytes-like "
242242
"object`, or iterable over elements of the appropriate type."
243243
msgstr ""
244-
"一个包含由 *typecode* 限制类型的条目的新数组，并由可选的 *initializer* "
245-
"值进行初始化，该值必须为一个列表、:term:`bytes-like object` 或包含正确类型元素的可迭代对象。"
244+
"一个包含由 *typecode* 限制类型的条目的新数组，并由可选的 *initializer* 值进行初始化，该值必须为一个列表、:term"
245+
":`bytes-like object` 或包含正确类型元素的可迭代对象。"
246246

247247
#: ../../library/array.rst:74
248248
msgid ""

‎library/audioop.po‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,8 +38,8 @@ msgstr ""
3838

3939
#: ../../library/audioop.rst:14
4040
msgid ""
41-
"Support for 24-bit samples was added. All functions now accept any :term"
42-
":`bytes-like object`. String input now results in an immediate error."
41+
"Support for 24-bit samples was added. All functions now accept any "
42+
":term:`bytes-like object`. String input now results in an immediate error."
4343
msgstr ""
4444
"增加了对 24 位样本的支持。现在，所有函数都接受任何 :term:`类字节串对象 <bytes-like "
4545
"object>`。而传入字符串会立即导致错误。"

0 commit comments

Comments
 (0)