| commit | e00c1d0c45975c0e9367f05f8c68bb32d68c2fbf | [log] [tgz] |
|---|---|---|
| author | Brian Curtin <brian@python.org> | Mon Feb 10 10:47:17 2020 -0700 |
| committer | GitHub <noreply@github.com> | Mon Feb 10 10:47:17 2020 -0700 |
| tree | 9d7d781ee1dac699930a018f28787be4deb5cebb | |
| parent | 29b3fc0a18f105de666fdd586b537f34e349766d [diff] |
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.