https://github.com/python/cpython/commit/e5ee784a7c04fd578b8711e1fd859295173f1830 commit: e5ee784a7c04fd578b8711e1fd859295173f1830 branch: 3.13 author: Miss Islington (bot) <31488909+miss-isling...@users.noreply.github.com> committer: terryjreedy <tjre...@udel.edu> date: 2025-02-15T03:37:05Z summary:
[3.13] gh-130106: Fix a typo in unittest.mock doc (GH-130107) (#130143) gh-130106: Fix a typo in unittest.mock doc (GH-130107) (cherry picked from commit d2e60d8e598b622573b68b80b4fbf98c021dd087) Co-authored-by: Srinivas Reddy Thatiparthy (తాటిపర్తి శ్రీనివాస్ రెడ్డి) <thatiparthysreeni...@gmail.com> files: M Doc/library/unittest.mock.rst diff --git a/Doc/library/unittest.mock.rst b/Doc/library/unittest.mock.rst index 514c6b7e615215..2c3574067a8407 100644 --- a/Doc/library/unittest.mock.rst +++ b/Doc/library/unittest.mock.rst @@ -1984,7 +1984,7 @@ Imagine we have a project that we want to test with the following structure:: Now we want to test ``some_function`` but we want to mock out ``SomeClass`` using :func:`patch`. The problem is that when we import module b, which we will have to -do then it imports ``SomeClass`` from module a. If we use :func:`patch` to mock out +do when it imports ``SomeClass`` from module a. If we use :func:`patch` to mock out ``a.SomeClass`` then it will have no effect on our test; module b already has a reference to the *real* ``SomeClass`` and it looks like our patching had no effect. _______________________________________________ Python-checkins mailing list -- python-checkins@python.org To unsubscribe send an email to python-checkins-le...@python.org https://mail.python.org/mailman3/lists/python-checkins.python.org/ Member address: arch...@mail-archive.com
