From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Tue, 10 May 2022 09:28:20 +0000 (-0700) Subject: [3.11] gh-92417: `unittest.mock` docs: remove references to Python <2.6 (GH-92539... X-Git-Tag: v3.11.0b2~126 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=c84f547d1db44a0f0ee238140552de014e1f7b43;p=thirdparty%2FPython%2Fcpython.git [3.11] gh-92417: `unittest.mock` docs: remove references to Python <2.6 (GH-92539) (GH-92606) (cherry picked from commit 6823ba4a9ee1a88102e835c5a278904f35588675) Co-authored-by: Alex Waygood Automerge-Triggered-By: GH:serhiy-storchaka --- diff --git a/Doc/library/unittest.mock-examples.rst b/Doc/library/unittest.mock-examples.rst index 24a18c684846..054efa812663 100644 --- a/Doc/library/unittest.mock-examples.rst +++ b/Doc/library/unittest.mock-examples.rst @@ -660,7 +660,7 @@ Applying the same patch to every test method If you want several patches in place for multiple test methods the obvious way is to apply the patch decorators to every method. This can feel like unnecessary -repetition. For Python 2.6 or more recent you can use :func:`patch` (in all its +repetition. Instead, you can use :func:`patch` (in all its various forms) as a class decorator. This applies the patches to all test methods on the class. A test method is identified by methods whose names start with ``test``:: diff --git a/Doc/library/unittest.mock.rst b/Doc/library/unittest.mock.rst index a3700ac07f1c..acc0d67541ae 100644 --- a/Doc/library/unittest.mock.rst +++ b/Doc/library/unittest.mock.rst @@ -2381,7 +2381,7 @@ FILTER_DIR .. data:: FILTER_DIR :data:`FILTER_DIR` is a module level variable that controls the way mock objects -respond to :func:`dir` (only for Python 2.6 or more recent). The default is ``True``, +respond to :func:`dir`. The default is ``True``, which uses the filtering described below, to only show useful members. If you dislike this filtering, or need to switch it off for diagnostic purposes, then set ``mock.FILTER_DIR = False``.