From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Wed, 11 May 2022 10:49:59 +0000 (-0700) Subject: [3.11] Fix typo in unittest.rst: addCleanupModule -> addModuleCleanup (GH-92631)... X-Git-Tag: v3.11.0b2~115 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=5ea8a93e1a35bf08153b5d02e9a332cd9b531241;p=thirdparty%2FPython%2Fcpython.git [3.11] Fix typo in unittest.rst: addCleanupModule -> addModuleCleanup (GH-92631) (GH-92659) (cherry picked from commit 38486ca212c0827d54e7b0d0b1e2c1ccc2bdad33) Co-authored-by: Mikhail Terekhov Automerge-Triggered-By: GH:serhiy-storchaka --- diff --git a/Doc/library/unittest.rst b/Doc/library/unittest.rst index f6bcba06d90e..e07a32b88b1c 100644 --- a/Doc/library/unittest.rst +++ b/Doc/library/unittest.rst @@ -2512,7 +2512,7 @@ To add cleanup code that must be run even in the case of an exception, use after :func:`setUpModule` if :func:`setUpModule` raises an exception. It is responsible for calling all the cleanup functions added by - :func:`addCleanupModule`. If you need cleanup functions to be called + :func:`addModuleCleanup`. If you need cleanup functions to be called *prior* to :func:`tearDownModule` then you can call :func:`doModuleCleanups` yourself.