diff options
| author | Brian Curtin <brian@python.org> | 2020-02-10 17:47:17 (GMT) |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-02-10 17:47:17 (GMT) |
| commit | e00c1d0c45975c0e9367f05f8c68bb32d68c2fbf (patch) | |
| tree | 9d7d781ee1dac699930a018f28787be4deb5cebb | |
| parent | 29b3fc0a18f105de666fdd586b537f34e349766d (diff) | |
| download | cpython-e00c1d0c45975c0e9367f05f8c68bb32d68c2fbf.zip cpython-e00c1d0c45975c0e9367f05f8c68bb32d68c2fbf.tar.gz cpython-e00c1d0c45975c0e9367f05f8c68bb32d68c2fbf.tar.bz2 | |
Remove note saying patch is straightforward (#18431)
While `unittest.mock.patch` is a great thing, it is not straightforward.
If it were straightforward there wouldn't be such a huge amount of
documentation for it, and frankly, when myself and others who I've
read about often struggle to figure out what on earth `patch()` wants,
coming to the docs to read that it's straightforward is not helpful.
| -rw-r--r-- | Doc/library/unittest.mock.rst | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/Doc/library/unittest.mock.rst b/Doc/library/unittest.mock.rst index 515bdd0..3643d1a 100644 --- a/Doc/library/unittest.mock.rst +++ b/Doc/library/unittest.mock.rst @@ -1327,8 +1327,7 @@ patch .. note:: - :func:`patch` is straightforward to use. The key is to do the patching in the - right namespace. See the section `where to patch`_. + The key is to do the patching in the right namespace. See the section `where to patch`_. .. function:: patch(target, new=DEFAULT, spec=None, create=False, spec_set=None, autospec=None, new_callable=None, **kwargs) |