We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
unittest.mock
1 parent df8091d commit d527d3bCopy full SHA for d527d3b
Doc/library/unittest.mock-examples.rst
@@ -863,9 +863,9 @@ Here's one solution that uses the :attr:`~Mock.side_effect`
863
functionality. If you provide a ``side_effect`` function for a mock then
864
``side_effect`` will be called with the same args as the mock. This gives us an
865
opportunity to copy the arguments and store them for later assertions. In this
866
-example I'm using *another* mock to store the arguments so that I can use the
+example we're using *another* mock to store the arguments so that we can use the
867
mock methods for doing the assertion. Again a helper function sets this up for
868
-me. ::
+us. ::
869
870
>>> from copy import deepcopy
871
>>> from unittest.mock import Mock, patch, DEFAULT
0 commit comments