[po] auto sync

github-actions[bot] · github-actions[bot] · commit 6b7df87e272b · 2022-06-09T02:59:03.000Z
diff --git a/library/unittest.mock-examples.po b/library/unittest.mock-examples.po
@@ -927,6 +927,8 @@ msgid ""
 " and using :data:`~Mock.side_effect` to delegate dictionary access to a real"
 " underlying dictionary that is under our control."
 msgstr ""
+"要做到这点我们可以用 :class:`MagicMock`，它的行为类似于字典，并会使用 :data:`~Mock.side_effect` "
+"将字典访问委托给下层的在我们控制之下的一个真正的字典。"
 
 #: ../../library/unittest.mock-examples.rst:974
 msgid ""
@@ -935,48 +937,57 @@ msgid ""
 "called with the key (and in the case of ``__setitem__`` the value too). We "
 "can also control what is returned."
 msgstr ""
+"当我们的 ``MagicMock`` 的 :meth:`__getitem__` 和 :meth:`__setitem__` "
+"方法被调用（即普通的字典访问操作）时 ``side_effect`` 将附带键（对于 ``__setitem__`` 则还将附带值）被调用。 "
+"我们也可以控制返回的对象。"
 
 #: ../../library/unittest.mock-examples.rst:978
 msgid ""
 "After the ``MagicMock`` has been used we can use attributes like "
 ":data:`~Mock.call_args_list` to assert about how the dictionary was used:"
 msgstr ""
+"在 ``MagicMock`` 被使用之后我们可以使用 :data:`~Mock.call_args_list` "
+"等属性来针对该字典是如何被使用的下断言。"
 
 #: ../../library/unittest.mock-examples.rst:994
 msgid ""
 "An alternative to using ``MagicMock`` is to use ``Mock`` and *only* provide "
 "the magic methods you specifically want:"
-msgstr ""
+msgstr "``MagicMock`` 的一个可用替代是使用 ``Mock`` 并 *仅仅* 提供你明确需要的魔术方法:"
 
 #: ../../library/unittest.mock-examples.rst:1001
 msgid ""
 "A *third* option is to use ``MagicMock`` but passing in ``dict`` as the "
 "*spec* (or *spec_set*) argument so that the ``MagicMock`` created only has "
 "dictionary magic methods available:"
 msgstr ""
+"*第三个* 选项是使用 ``MagicMock`` 但传入 ``dict`` 作为 *spec* (或 *spec_set*) 参数以使得所创建的 "
+"``MagicMock`` 只有字典魔术方法是可用的:"
 
 #: ../../library/unittest.mock-examples.rst:1009
 msgid ""
 "With these side effect functions in place, the ``mock`` will behave like a "
 "normal dictionary but recording the access. It even raises a :exc:`KeyError`"
 " if you try to access a key that doesn't exist."
 msgstr ""
+"通过提供这些附带影响函数，``mock`` 的行为将类似于普通字典但又会记录所有访问。 如果你尝试访问一个不存在的键它甚至会引发 "
+":exc:`KeyError`。"
 
 #: ../../library/unittest.mock-examples.rst:1028
 msgid ""
 "After it has been used you can make assertions about the access using the "
 "normal mock methods and attributes:"
-msgstr ""
+msgstr "在它被使用之后你可以使用普通的 mock 方法和属性进行有关访问操作的断言:"
 
 #: ../../library/unittest.mock-examples.rst:1040
 msgid "Mock subclasses and their attributes"
-msgstr ""
+msgstr "模拟子类及其属性"
 
 #: ../../library/unittest.mock-examples.rst:1042
 msgid ""
 "There are various reasons why you might want to subclass :class:`Mock`. One "
 "reason might be to add helper methods. Here's a silly example:"
-msgstr ""
+msgstr "你可能出于各种原因想要子类化 :class:`Mock`。 其中一个可能的原因是为了添加辅助方法。 下面是一个笨兮兮的示例:"
 
 #: ../../library/unittest.mock-examples.rst:1058
 msgid ""
@@ -987,6 +998,9 @@ msgid ""
 "methods then they'll also be available on the attributes and return value "
 "mock of instances of your subclass."
 msgstr ""
+"The standard behaviour for ``Mock`` 实例的标准行为是属性和返回值 mock 具有与它们所访问的 mock "
+"相同的类型。 这将确保 ``Mock`` 的属性均为 ``Mocks`` 而 ``MagicMock`` 的属性均为 ``MagicMocks`` "
+"[#]_。 因此如果你通过子类化来添加辅助方法那么它们也将在你的子类的实例的属性和返回值 mock 上可用。"
 
 #: ../../library/unittest.mock-examples.rst:1074
 msgid ""
