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

Skip to content

Commit 3bf16a5

Browse files
github-actions[bot]github-actions[bot]
committed
[po] auto sync
1 parent 29611ea commit 3bf16a5

26 files changed

Lines changed: 2066 additions & 2206 deletions

‎.stat.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
{"translation": "93.74%", "updated_at": "2024-02-02T06:55:54Z"}
1+
{"translation": "93.46%", "updated_at": "2024-02-02T14:55:47Z"}

‎c-api/object.po‎

Lines changed: 55 additions & 64 deletions
Large diffs are not rendered by default.

‎howto/logging.po‎

Lines changed: 59 additions & 79 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ msgid ""
2222
msgstr ""
2323
"Project-Id-Version: Python 3.12\n"
2424
"Report-Msgid-Bugs-To: \n"
25-
"POT-Creation-Date: 2024-01-05 14:14+0000\n"
25+
"POT-Creation-Date: 2024-02-02 14:13+0000\n"
2626
"PO-Revision-Date: 2021-06-28 00:53+0000\n"
2727
"Last-Translator: Freesand Leo <[email protected]>, 2024\n"
2828
"Language-Team: Chinese (China) (https://app.transifex.com/python-doc/teams/5390/zh_CN/)\n"
@@ -806,13 +806,11 @@ msgstr "处理器中很少有方法可供应用程序开发人员使用。使用
806806
msgid ""
807807
"The :meth:`~Handler.setLevel` method, just as in logger objects, specifies "
808808
"the lowest severity that will be dispatched to the appropriate destination."
809-
" Why are there two :func:`setLevel` methods? The level set in the logger "
810-
"determines which severity of messages it will pass to its handlers. The "
811-
"level set in each handler determines which messages that handler will send "
812-
"on."
809+
" Why are there two :meth:`~Handler.setLevel` methods? The level set in the"
810+
" logger determines which severity of messages it will pass to its handlers."
811+
" The level set in each handler determines which messages that handler will "
812+
"send on."
813813
msgstr ""
814-
":meth:`~handler.setLevel` 方法，就像在记录器对象中一样，指定将被分派到适当目标的最低严重性。为什么有两个 "
815-
":func:`setLevel` 方法？记录器中设置的级别确定将传递给其处理器的消息的严重性。每个处理器中设置的级别确定该处理器将发送哪些消息。"
816814

817815
#: ../../howto/logging.rst:528
818816
msgid ""
@@ -1055,55 +1053,41 @@ msgstr "如果没有提供配置会发生什么"
10551053
msgid ""
10561054
"If no logging configuration is provided, it is possible to have a situation "
10571055
"where a logging event needs to be output, but no handlers can be found to "
1058-
"output the event. The behaviour of the logging package in these "
1059-
"circumstances is dependent on the Python version."
1056+
"output the event."
10601057
msgstr ""
1061-
"如果未提供日志记录配置，则可能出现需要输出日志记录事件但无法找到输出事件的处理器的情况。 在这些情况下，logging 包的行为取决于 Python "
1062-
"版本。"
10631058

1064-
#: ../../howto/logging.rst:781
1059+
#: ../../howto/logging.rst:780
1060+
msgid ""
1061+
"The event is output using a 'handler of last resort', stored in "
1062+
":data:`lastResort`. This internal handler is not associated with any logger,"
1063+
" and acts like a :class:`~logging.StreamHandler` which writes the event "
1064+
"description message to the current value of ``sys.stderr`` (therefore "
1065+
"respecting any redirections which may be in effect). No formatting is done "
1066+
"on the message - just the bare event description message is printed. The "
1067+
"handler's level is set to ``WARNING``, so all events at this and greater "
1068+
"severities will be output."
1069+
msgstr ""
1070+
1071+
#: ../../howto/logging.rst:791
10651072
msgid "For versions of Python prior to 3.2, the behaviour is as follows:"
10661073
msgstr "对于 3.2 之前的 Python 版本，行为如下："
10671074

1068-
#: ../../howto/logging.rst:783
1075+
#: ../../howto/logging.rst:793
10691076
msgid ""
1070-
"If *logging.raiseExceptions* is ``False`` (production mode), the event is "
1077+
"If :data:`raiseExceptions` is ``False`` (production mode), the event is "
10711078
"silently dropped."
1072-
msgstr "如果 *logging.raiseExceptions* 为 ``False`` （生产模式），则会以静默方式丢弃该事件。"
1079+
msgstr ""
10731080

1074-
#: ../../howto/logging.rst:786
1081+
#: ../../howto/logging.rst:796
10751082
msgid ""
1076-
"If *logging.raiseExceptions* is ``True`` (development mode), a message 'No "
1083+
"If :data:`raiseExceptions` is ``True`` (development mode), a message 'No "
10771084
"handlers could be found for logger X.Y.Z' is printed once."
10781085
msgstr ""
1079-
"如果 *logging.raiseExceptions* 为 ``True`` （开发模式），则会打印一条消息 'No handlers could "
1080-
"be found for logger X.Y.Z'。"
10811086

1082-
#: ../../howto/logging.rst:789
1083-
msgid "In Python 3.2 and later, the behaviour is as follows:"
1084-
msgstr "在 Python 3.2 及更高版本中，行为如下："
1085-
1086-
#: ../../howto/logging.rst:791
1087+
#: ../../howto/logging.rst:799
10871088
msgid ""
1088-
"The event is output using a 'handler of last resort', stored in "
1089-
"``logging.lastResort``. This internal handler is not associated with any "
1090-
"logger, and acts like a :class:`~logging.StreamHandler` which writes the "
1091-
"event description message to the current value of ``sys.stderr`` (therefore "
1092-
"respecting any redirections which may be in effect). No formatting is done "
1093-
"on the message - just the bare event description message is printed. The "
1094-
"handler's level is set to ``WARNING``, so all events at this and greater "
1095-
"severities will be output."
1089+
"To obtain the pre-3.2 behaviour, :data:`lastResort` can be set to ``None``."
10961090
msgstr ""
1097-
"事件使用 “最后的处理器” 输出，存储在 ``logging.lastResort`` 中。 这个内部处理器与任何记录器都没有关联，它的作用类似于 "
1098-
":class:`~logging.StreamHandler` ，它将事件描述消息写入 ``sys.stderr`` "
1099-
"的当前值（因此服从任何可能的重定向影响）。 没有对消息进行格式化——只打印裸事件描述消息。处理器的级别设置为 "
1100-
"``WARNING``，因此将输出此级别和更高级别的所有事件。"
1101-
1102-
#: ../../howto/logging.rst:800
1103-
msgid ""
1104-
"To obtain the pre-3.2 behaviour, ``logging.lastResort`` can be set to "
1105-
"``None``."
1106-
msgstr "要获得 3.2 之前的行为，可以设置 ``logging.lastResort`` 为 ``None``。"
11071091

11081092
#: ../../howto/logging.rst:805
11091093
msgid "Configuring Logging for a Library"
@@ -1457,12 +1441,10 @@ msgstr ""
14571441
#: ../../howto/logging.rst:1001
14581442
msgid ""
14591443
"For formatting multiple messages in a batch, instances of "
1460-
":class:`~handlers.BufferingFormatter` can be used. In addition to the format"
1461-
" string (which is applied to each message in the batch), there is provision "
1462-
"for header and trailer format strings."
1444+
":class:`BufferingFormatter` can be used. In addition to the format string "
1445+
"(which is applied to each message in the batch), there is provision for "
1446+
"header and trailer format strings."
14631447
msgstr ""
1464-
"要批量格式化多个消息，可以使用 :class:`~handlers.BufferingFormatter` "
1465-
"的实例。除了格式字符串（应用于批处理中的每个消息）之外，还提供了标题和尾部格式字符串。"
14661448

14671449
#: ../../howto/logging.rst:1006
14681450
msgid ""
@@ -1522,7 +1504,7 @@ msgstr ""
15221504
":class:`Handler` 中的 :meth:`~handler.handleError` 的默认实现是检查是否设置了模块级变量 "
15231505
":data:`raiseExceptions`。如有设置，则会将回溯打印到 :data:`sys.stderr`。如果未设置，则忽略异常。"
15241506

1525-
#: ../../howto/logging.rst:1038
1507+
#: ../../howto/logging.rst:1039
15261508
msgid ""
15271509
"The default value of :data:`raiseExceptions` is ``True``. This is because "
15281510
"during development, you typically want to be notified of any exceptions that"
@@ -1532,11 +1514,11 @@ msgstr ""
15321514
":data:`raiseExceptions` 的默认值是 ``True``。这是因为在开发期间，你通常想要在发生异常时收到通知。建议你将 "
15331515
":data:`raiseExceptions` 设为 ``False`` 供生产环境下使用。"
15341516

1535-
#: ../../howto/logging.rst:1048
1517+
#: ../../howto/logging.rst:1049
15361518
msgid "Using arbitrary objects as messages"
15371519
msgstr "使用任意对象作为消息"
15381520

1539-
#: ../../howto/logging.rst:1050
1521+
#: ../../howto/logging.rst:1051
15401522
msgid ""
15411523
"In the preceding sections and examples, it has been assumed that the message"
15421524
" passed when logging the event is a string. However, this is not the only "
@@ -1552,11 +1534,11 @@ msgstr ""
15521534
"str__` 方法。实际上，如果你愿意，你可以完全避免计算字符串表示。例如， :class:`~handlers.SocketHandler` 用 "
15531535
"pickle 处理事件后，通过网络发送。"
15541536

1555-
#: ../../howto/logging.rst:1061
1537+
#: ../../howto/logging.rst:1062
15561538
msgid "Optimization"
15571539
msgstr "优化"
15581540

1559-
#: ../../howto/logging.rst:1063
1541+
#: ../../howto/logging.rst:1064
15601542
msgid ""
15611543
"Formatting of message arguments is deferred until it cannot be avoided. "
15621544
"However, computing the arguments passed to the logging method can also be "
@@ -1570,15 +1552,13 @@ msgstr ""
15701552
" :meth:`~Logger.isEnabledFor` 方法，该方法接受一个 level 参数，如果记录器为该级别的调用创建了该事件，则返回 "
15711553
"true 。 你可以写这样的代码::"
15721554

1573-
#: ../../howto/logging.rst:1075
1555+
#: ../../howto/logging.rst:1076
15741556
msgid ""
15751557
"so that if the logger's threshold is set above ``DEBUG``, the calls to "
1576-
":func:`expensive_func1` and :func:`expensive_func2` are never made."
1558+
"``expensive_func1`` and ``expensive_func2`` are never made."
15771559
msgstr ""
1578-
"因此，如果记录器的阈值设置在“DEBUG”以上，则永远不会调用 :func:`expensive_func1` 和 "
1579-
":func:`expensive_func2` 。"
15801560

1581-
#: ../../howto/logging.rst:1078
1561+
#: ../../howto/logging.rst:1079
15821562
msgid ""
15831563
"In some cases, :meth:`~Logger.isEnabledFor` can itself be more expensive "
15841564
"than you'd like (e.g. for deeply nested loggers where an explicit level is "
@@ -1594,27 +1574,27 @@ msgstr ""
15941574
" :meth:`~Logger.isEnabledFor` "
15951575
"，并使用它而不是每次调用方法。在日志记录配置在应用程序运行时动态更改（这不常见）时，只需要重新计算这样的缓存值即可。"
15961576

1597-
#: ../../howto/logging.rst:1087
1577+
#: ../../howto/logging.rst:1088
15981578
msgid ""
15991579
"There are other optimizations which can be made for specific applications "
16001580
"which need more precise control over what logging information is collected. "
16011581
"Here's a list of things you can do to avoid processing during logging which "
16021582
"you don't need:"
16031583
msgstr "对于需要对收集的日志信息进行更精确控制的特定应用程序，还可以进行其他优化。以下列出了在日志记录过程中您可以避免的非必须处理操作："
16041584

1605-
#: ../../howto/logging.rst:1093
1585+
#: ../../howto/logging.rst:1094
16061586
msgid "What you don't want to collect"
16071587
msgstr "你不想收集的内容"
16081588

1609-
#: ../../howto/logging.rst:1093
1589+
#: ../../howto/logging.rst:1094
16101590
msgid "How to avoid collecting it"
16111591
msgstr "如何避免收集它"
16121592

1613-
#: ../../howto/logging.rst:1095
1593+
#: ../../howto/logging.rst:1096
16141594
msgid "Information about where calls were made from."
16151595
msgstr "有关调用来源的信息"
16161596

1617-
#: ../../howto/logging.rst:1095
1597+
#: ../../howto/logging.rst:1096
16181598
msgid ""
16191599
"Set ``logging._srcfile`` to ``None``. This avoids calling "
16201600
":func:`sys._getframe`, which may help to speed up your code in environments "
@@ -1623,41 +1603,41 @@ msgstr ""
16231603
"将 ``logging._srcfile`` 设置为 ``None`` 。这避免了调用 :func:`sys._getframe` ，如果 PyPy "
16241604
"支持 Python 3.x ，这可能有助于加速 PyPy （无法加速使用 :func:`sys._getframe` 的代码）等环境中的代码。"
16251605

1626-
#: ../../howto/logging.rst:1101
1606+
#: ../../howto/logging.rst:1102
16271607
msgid "Threading information."
16281608
msgstr "线程信息"
16291609

1630-
#: ../../howto/logging.rst:1101
1610+
#: ../../howto/logging.rst:1102
16311611
msgid "Set ``logging.logThreads`` to ``False``."
16321612
msgstr "将 ``logging.logThreads`` 设为 ``False``。"
16331613

1634-
#: ../../howto/logging.rst:1103
1614+
#: ../../howto/logging.rst:1104
16351615
msgid "Current process ID (:func:`os.getpid`)"
16361616
msgstr "当前进程 ID (:func:`os.getpid`)"
16371617

1638-
#: ../../howto/logging.rst:1103
1618+
#: ../../howto/logging.rst:1104
16391619
msgid "Set ``logging.logProcesses`` to ``False``."
16401620
msgstr "将 ``logging.logProcesses`` 设为 ``False``。"
16411621

1642-
#: ../../howto/logging.rst:1105
1622+
#: ../../howto/logging.rst:1106
16431623
msgid ""
16441624
"Current process name when using ``multiprocessing`` to manage multiple "
16451625
"processes."
16461626
msgstr "当使用 ``multiprocessing`` 来管理多个进程时的当前进程名称。"
16471627

1648-
#: ../../howto/logging.rst:1105
1628+
#: ../../howto/logging.rst:1106
16491629
msgid "Set ``logging.logMultiprocessing`` to ``False``."
16501630
msgstr "将 ``logging.logMultiprocessing`` 设为 ``False``。"
16511631

1652-
#: ../../howto/logging.rst:1108
1632+
#: ../../howto/logging.rst:1109
16531633
msgid "Current :class:`asyncio.Task` name when using ``asyncio``."
16541634
msgstr "在使用 ``asyncio`` 时的当前 :class:`asyncio.Task`。"
16551635

1656-
#: ../../howto/logging.rst:1108
1636+
#: ../../howto/logging.rst:1109
16571637
msgid "Set ``logging.logAsyncioTasks`` to ``False``."
16581638
msgstr "将 ``logging.logAsyncioTasks`` 设为 ``False``。"
16591639

1660-
#: ../../howto/logging.rst:1112
1640+
#: ../../howto/logging.rst:1113
16611641
msgid ""
16621642
"Also note that the core logging module only includes the basic handlers. If "
16631643
"you don't import :mod:`logging.handlers` and :mod:`logging.config`, they "
@@ -1666,34 +1646,34 @@ msgstr ""
16661646
"另请注意，核心日志记录模块仅包含基本处理器。如果你不导入 :mod:`logging.handlers` 和 :mod:`logging.config`"
16671647
" ，它们将不会占用任何内存。"
16681648

1669-
#: ../../howto/logging.rst:1119
1649+
#: ../../howto/logging.rst:1120
16701650
msgid "Other resources"
16711651
msgstr "其他资源"
16721652

1673-
#: ../../howto/logging.rst:1124
1653+
#: ../../howto/logging.rst:1125
16741654
msgid "Module :mod:`logging`"
16751655
msgstr "模块 :mod:`logging`"
16761656

1677-
#: ../../howto/logging.rst:1124
1657+
#: ../../howto/logging.rst:1125
16781658
msgid "API reference for the logging module."
16791659
msgstr "日志记录模块的 API 参考。"
16801660

1681-
#: ../../howto/logging.rst:1127
1661+
#: ../../howto/logging.rst:1128
16821662
msgid "Module :mod:`logging.config`"
16831663
msgstr ":mod:`logging.config` 模块"
16841664

1685-
#: ../../howto/logging.rst:1127
1665+
#: ../../howto/logging.rst:1128
16861666
msgid "Configuration API for the logging module."
16871667
msgstr "日志记录模块的配置 API 。"
16881668

1689-
#: ../../howto/logging.rst:1130
1669+
#: ../../howto/logging.rst:1131
16901670
msgid "Module :mod:`logging.handlers`"
16911671
msgstr ":mod:`logging.handlers` 模块"
16921672

1693-
#: ../../howto/logging.rst:1130
1673+
#: ../../howto/logging.rst:1131
16941674
msgid "Useful handlers included with the logging module."
16951675
msgstr "日志记录模块附带的有用处理器。"
16961676

1697-
#: ../../howto/logging.rst:1132
1677+
#: ../../howto/logging.rst:1133
16981678
msgid ":ref:`A logging cookbook <logging-cookbook>`"
16991679
msgstr ":ref:`日志操作手册 <logging-cookbook>`"

0 commit comments

Comments
 (0)