feat: to rst:935

Author: ken71301

library/unittest.mock-examples.po

@@ -8,7 +8,7 @@ msgstr ""
 "Project-Id-Version: Python 3.12\n"
 "Report-Msgid-Bugs-To: \n"
 "POT-Creation-Date: 2023-09-09 00:03+0000\n"
-"PO-Revision-Date: 2024-03-11 22:03+0800\n"
+"PO-Revision-Date: 2024-03-12 21:41+0800\n"
 "Last-Translator: Liang-Bo Wang <[email protected]>\n"
 "Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-"
 "tw)\n"
@@ -905,20 +905,23 @@ msgstr ""
 msgid ""
 "Here's some example code that shows the problem. Imagine the following "
 "functions defined in 'mymodule'::"
-msgstr ""
+msgstr "這是一些秀出問題的程式碼範例。 想像 'mymodule' 中定義以下函式： ::"
 
 #: ../../library/unittest.mock-examples.rst:843
 msgid ""
 "When we try to test that ``grob`` calls ``frob`` with the correct argument "
 "look what happens::"
 msgstr ""
+"當我們嘗試測試 ``grob`` 使用正確的引數呼叫 ``frob`` 時，看看會發生什麼： ::"
 
 #: ../../library/unittest.mock-examples.rst:858
 msgid ""
 "One possibility would be for mock to copy the arguments you pass in. This "
 "could then cause problems if you do assertions that rely on object identity "
 "for equality."
 msgstr ""
+"一種可能是讓 mock 複製你傳入的引數。如果你為了相等性執行依賴於物件識別性的斷"
+"言，這可能會導致問題。"
 
 #: ../../library/unittest.mock-examples.rst:862
 msgid ""
@@ -930,27 +933,39 @@ msgid ""
 "methods for doing the assertion. Again a helper function sets this up for "
 "me. ::"
 msgstr ""
+"以下是一種使用 :attr:`~Mock.side_effect` 功能的解法。如果你為 mock 提供一個 "
+"``side_effect`` 函式，則 ``side_effect`` 將被使用與 mock 相同的引數呼叫。這使"
+"我們有機會複製引數並將其儲存以供之後的斷言。在這個範例中，我們使用\\ *另一個"
+"* mock 來儲存引數，以便我們可以使用 mock 方法來執行斷言。同樣的，有一個輔助函"
+"式為我們設定了這些。： ::"
 
 #: ../../library/unittest.mock-examples.rst:891
 msgid ""
 "``copy_call_args`` is called with the mock that will be called. It returns a "
 "new mock that we do the assertion on. The ``side_effect`` function makes a "
 "copy of the args and calls our ``new_mock`` with the copy."
 msgstr ""
+"``copy_call_args`` 與將要被呼叫的 mock 一起被呼叫。它回傳一個我們會對其進行斷"
+"言的新的 mock。``side_effect`` 函式建立引數們的副本，並用該副本呼叫我們的 "
+"``new_mock``。"
 
 #: ../../library/unittest.mock-examples.rst:897
 msgid ""
 "If your mock is only going to be used once there is an easier way of "
 "checking arguments at the point they are called. You can simply do the "
 "checking inside a ``side_effect`` function."
 msgstr ""
+"如果你的 mock 只會被使用一次，則有一種更簡單的方法可以在呼叫引數時檢查它們。"
+"你可以簡單地在 ``side_effect`` 函式內進行檢查。"
 
 #: ../../library/unittest.mock-examples.rst:911
 msgid ""
 "An alternative approach is to create a subclass of :class:`Mock` or :class:"
 "`MagicMock` that copies (using :func:`copy.deepcopy`) the arguments. Here's "
 "an example implementation:"
 msgstr ""
+"另一種方法是建立 :class:`Mock` 或 :class:`MagicMock` 的子類別來複製（使用 :"
+"func:`copy.deepcopy`\\ ）引數。這是一個實作的例子："
 
 #: ../../library/unittest.mock-examples.rst:935
 msgid ""
@@ -959,6 +974,9 @@ msgid ""
 "That means all children of a ``CopyingMock`` will also have the type "
 "``CopyingMock``."
 msgstr ""
+"當你將 ``Mock`` 或 ``MagicMock`` 子類別化時，所有屬性會被動態建立，且 "
+"``return_value`` 會自動使用你的子類別。這代表著 ``CopyingMock`` 的所有子代 "
+"(child) 也會具有``CopyingMock`` 型別。"
 
 #: ../../library/unittest.mock-examples.rst:941
 msgid "Nesting Patches"