From 0fa2944e4d7e0b62cadb9e12d91129a5aecefc6e Mon Sep 17 00:00:00 2001 From: AlexWaygood Date: Mon, 9 May 2022 09:01:50 +0100 Subject: [PATCH] gh-92417: `unittest.mock` docs: remove references to Python <2.6 --- Doc/library/unittest.mock-examples.rst | 2 +- Doc/library/unittest.mock.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/library/unittest.mock-examples.rst b/Doc/library/unittest.mock-examples.rst index 24a18c68484686..054efa81266326 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 a3700ac07f1c1a..acc0d67541ae82 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``.