1212# 1lin24 <[email protected] >, 20191313# Shengjing Zhu <[email protected] >, 20191414# ppcfish <[email protected] >, 201915+ # Leo Li <[email protected] >, 20191516#
1617#, fuzzy
1718msgid ""
@@ -20,7 +21,7 @@ msgstr ""
2021"Report-Msgid-Bugs-To : \n "
2122"POT-Creation-Date : 2019-10-04 11:35+0000\n "
2223"PO-Revision-Date : 2017-02-16 23:17+0000\n "
23- "Last-Translator : ppcfish <ppcfish@gmail .com>, 2019\n "
24+ "Last-Translator : Leo Li <foxleoly@hotmail .com>, 2019\n "
2425"Language-Team : Chinese (China) (https://www.transifex.com/python-doc/teams/5390/zh_CN/)\n "
2526"MIME-Version : 1.0\n "
2627"Content-Type : text/plain; charset=UTF-8\n "
@@ -130,6 +131,10 @@ msgid ""
130131"``logging.getLogger(__name__)``. That's because in a module, ``__name__`` "
131132"is the module's name in the Python package namespace."
132133msgstr ""
134+ "``name`` 是潜在的周期分割层级值, 像``foo.bar.baz`` (例如, "
135+ "抛出的可以只是明文的``foo``)。Loggers是进一步在子层次列表的更高loggers列表。例如,有个名叫``foo``的logger,名叫``foo.bar``,``foo.bar.baz``,和"
136+ " ``foo.bam`` 都是 ``foo``的衍生logger。logger的名字分级类似Python "
137+ "包的层级,并且相同的如果你组织你的loggers在每模块级别基本上使用推荐的结构``logging.getLogger(__name__)``。这是因为在模块里,在Python包的命名空间的模块名为``__name__``。"
133138
134139#: ../../library/logging.rst:74
135140msgid ""
@@ -139,6 +144,8 @@ msgid ""
139144"ancestor loggers' handlers - neither the level nor filters of the ancestor "
140145"loggers in question are considered."
141146msgstr ""
147+ "如果这个属性为真,记录到这个记录器的事件将会传递给这个高级别管理器的记录器(原型),此外任何关联到这个记录器的管理器。消息会直接传递给原型记录器的管理器"
148+ " - 既不是这个原型记录器的级别也不是过滤器是在考虑的问题。"
142149
143150#: ../../library/logging.rst:80
144151msgid ""
0 commit comments