diff options
| author | Tony Newton / Teng Liu <657339595@qq.com> | 2022-10-26 15:12:28 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-10-26 15:12:28 +0800 |
| commit | 30e1917f1c2d8e05556a47af1130c149bab7d783 (patch) | |
| tree | 19740bc2384d5fc41c2c18a562e5b604104f4e9a /doc/source | |
| parent | 6a5086c9b875ea06fe5c6411cdc225188f10a7bb (diff) | |
| download | numpy-30e1917f1c2d8e05556a47af1130c149bab7d783.tar.gz | |
DOC: fix typo in advanced_debugging.rst [skip ci]
Diffstat (limited to 'doc/source')
| -rw-r--r-- | doc/source/dev/development_advanced_debugging.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/source/dev/development_advanced_debugging.rst b/doc/source/dev/development_advanced_debugging.rst index 2dbd6ac22..efd78cfad 100644 --- a/doc/source/dev/development_advanced_debugging.rst +++ b/doc/source/dev/development_advanced_debugging.rst @@ -23,7 +23,7 @@ But for example memory leaks can be particularly subtle or difficult to narrow down. We do not expect any of these tools to be run by most contributors. -However, you can ensure that we can track down such issues more easily easier: +However, you can ensure that we can track down such issues more easily: * Tests should cover all code paths, including error paths. * Try to write short and simple tests. If you have a very complicated test |