]> git.ipfire.org Git - thirdparty/Python/cpython.git/commitdiff
[3.12] gh-130106: Fix a typo in unittest.mock doc (GH-130107) (#130144)
authorMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Sat, 15 Feb 2025 03:59:08 +0000 (04:59 +0100)
committerGitHub <noreply@github.com>
Sat, 15 Feb 2025 03:59:08 +0000 (03:59 +0000)
gh-130106: Fix a typo in unittest.mock doc (GH-130107)
(cherry picked from commit d2e60d8e598b622573b68b80b4fbf98c021dd087)

Co-authored-by: Srinivas Reddy Thatiparthy (తాటిపర్తి శ్రీనివాస్ రెడ్డి) <thatiparthysreenivas@gmail.com>
Doc/library/unittest.mock.rst

index 84f34a0696a26cc8ae33cc971ebe7214717475d5..b44b8dc2d20a57c0f3eb906f5f2fecc9c7fbc264 100644 (file)
@@ -1958,7 +1958,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.