https://github.com/python/cpython/commit/d527d3bf8beb9cd26c179f2c0111d635cdaa9cd3
commit: d527d3bf8beb9cd26c179f2c0111d635cdaa9cd3
branch: main
author: dereckduran <[email protected]>
committer: hugovk <[email protected]>
date: 2025-11-17T13:44:44+02:00
summary:
gh-62480: De-personalize "Coping with mutable arguments" section in
`unittest.mock` examples (#141323)
files:
M Doc/library/unittest.mock-examples.rst
diff --git a/Doc/library/unittest.mock-examples.rst
b/Doc/library/unittest.mock-examples.rst
index 6af4298d44f532..61c75b5a03b103 100644
--- a/Doc/library/unittest.mock-examples.rst
+++ b/Doc/library/unittest.mock-examples.rst
@@ -863,9 +863,9 @@ Here's one solution that uses the :attr:`~Mock.side_effect`
functionality. If you provide a ``side_effect`` function for a mock then
``side_effect`` will be called with the same args as the mock. This gives us an
opportunity to copy the arguments and store them for later assertions. In this
-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
mock methods for doing the assertion. Again a helper function sets this up for
-me. ::
+us. ::
>>> from copy import deepcopy
>>> from unittest.mock import Mock, patch, DEFAULT
_______________________________________________
Python-checkins mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3//lists/python-checkins.python.org
Member address: [email protected]
