[po] auto sync

github-actions[bot] · github-actions[bot] · commit c3812c66c8bf · 2022-06-05T08:20:53.000Z
diff --git a/library/unittest.mock-examples.po b/library/unittest.mock-examples.po
@@ -372,7 +372,7 @@ msgid ""
 "they are looked up. This is normally straightforward, but for a quick guide "
 "read :ref:`where to patch <where-to-patch>`."
 msgstr ""
-"在查找对象的名称空间中修补对象使用 :func:`patch` 。使用起来很简单，阅读 :ref:`在哪里打补丁 <where-to-patch>` "
+"在查找对象的名称空间中修补对象使用 :func:`patch` 。使用起来很简单，阅读 :ref:`补丁的位置 <where-to-patch>` "
 "来快速上手。"
 
 #: ../../library/unittest.mock-examples.rst:374
@@ -597,12 +597,17 @@ msgid ""
 "When the mock date class is called a real date will be constructed and "
 "returned by ``side_effect``. ::"
 msgstr ""
+"这里使用 :func:`patch 装饰器 <patch>` 来模拟被测试模块中的 ``date`` 类。 模拟 date 类中的 "
+":attr:`side_effect` 属性随后被设为一个返回真实日期的 lambda 函数。 当模拟 date 类被调用时将由 "
+"``side_effect`` 构造并返回一个真实日期。 ::"
 
 #: ../../library/unittest.mock-examples.rst:602
 msgid ""
 "Note that we don't patch :class:`datetime.date` globally, we patch ``date`` "
 "in the module that *uses* it. See :ref:`where to patch <where-to-patch>`."
 msgstr ""
+"请注意我们没有在全局范围上修补 :class:`datetime.date`，我们只是在 *使用* 它的模块中给 ``date`` 打补丁。 参见 "
+":ref:`补丁的位置 <where-to-patch>`。"
 
 #: ../../library/unittest.mock-examples.rst:605
 msgid ""
@@ -611,29 +616,34 @@ msgid ""
 "find yourself having to calculate an expected result using exactly the same "
 "algorithm as the code under test, which is a classic testing anti-pattern."
 msgstr ""
+"当 ``date.today()`` 被调用时将返回一个已知的日期，但对 ``date(...)`` 构造器的调用仍会返回普通的日期。 "
+"如果不是这样你会发现你必须使用与被测试的代码完全相同的算法来计算出预期的结果，这是测试工作中的一个经典的反模式。"
 
 #: ../../library/unittest.mock-examples.rst:610
 msgid ""
 "Calls to the date constructor are recorded in the ``mock_date`` attributes "
 "(``call_count`` and friends) which may also be useful for your tests."
 msgstr ""
+"对 date 构造器的调用会被记录在 ``mock_date`` 属性中 (``call_count`` 等)，它们也可能对你的测试有用处。"
 
 #: ../../library/unittest.mock-examples.rst:613
 msgid ""
 "An alternative way of dealing with mocking dates, or other builtin classes, "
 "is discussed in `this blog entry <https://williambert.online/2011/07/how-to-"
 "unit-testing-in-django-with-mocking-and-patching/>`_."
 msgstr ""
+"有关处理模块日期或其他内置类的一种替代方式的讨论请参见 `这篇博客文章 <https://williambert.online/2011/07/how-"
+"to-unit-testing-in-django-with-mocking-and-patching/>`_。"
 
 #: ../../library/unittest.mock-examples.rst:619
 msgid "Mocking a Generator Method"
-msgstr ""
+msgstr "模拟生成器方法"
 
 #: ../../library/unittest.mock-examples.rst:621
 msgid ""
 "A Python generator is a function or method that uses the :keyword:`yield` "
 "statement to return a series of values when iterated over [#]_."
-msgstr ""
+msgstr "Python 生成器是指在被迭代时使用 :keyword:`yield` 语句来返回一系列值的函数或方法 [#]_。"
 
 #: ../../library/unittest.mock-examples.rst:624
 msgid ""
@@ -642,15 +652,17 @@ msgid ""
 "iteration is :meth:`~container.__iter__`, so we can mock this using a "
 ":class:`MagicMock`."
 msgstr ""
+"调用生成器方法 / 函数将返回生成器对象。 生成器对象随后会被迭代。 迭代操作对应的协议方法是 "
+":meth:`~container.__iter__`，因此我们可以使用 :class:`MagicMock` 来模拟它。"
 
 #: ../../library/unittest.mock-examples.rst:629
 msgid ""
 "Here's an example class with an \"iter\" method implemented as a generator:"
-msgstr ""
+msgstr "以下是一个使用 \"iter\" 方法模拟为生成器的示例类:"
 
 #: ../../library/unittest.mock-examples.rst:641
 msgid "How would we mock this class, and in particular its \"iter\" method?"
-msgstr ""
+msgstr "我们要如何模拟这个类，特别是它的 \"iter\" 方法呢？"
 
 #: ../../library/unittest.mock-examples.rst:643
 msgid ""
diff --git a/library/unittest.mock.po b/library/unittest.mock.po
@@ -1696,7 +1696,7 @@ msgstr ""
 
 #: ../../library/unittest.mock.rst:1899
 msgid "Where to patch"
-msgstr "补丁的目标"
+msgstr "补丁的位置"
 
 #: ../../library/unittest.mock.rst:1901
 msgid ""
