diff options
author | luz.paz <luzpaz@users.noreply.github.com> | 2018-03-30 09:33:39 -0400 |
---|---|---|
committer | luz.paz <luzpaz@users.noreply.github.com> | 2018-03-30 09:33:39 -0400 |
commit | 108d01a0a4eea38ed5b8e88de34ee2d0324fec65 (patch) | |
tree | c8ea966bbb29aec9588e712cd8c7230d63ac89e0 /numpy/doc/subclassing.py | |
parent | f879b158ab59e77fec9ecbb6b5fb988ba95afc4f (diff) | |
download | numpy-108d01a0a4eea38ed5b8e88de34ee2d0324fec65.tar.gz |
DOC: Fix minor typos
Found via `codespell -q 3 -I ../numpy-whitelist.txt`
Diffstat (limited to 'numpy/doc/subclassing.py')
-rw-r--r-- | numpy/doc/subclassing.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/numpy/doc/subclassing.py b/numpy/doc/subclassing.py index 467e31cea..3be3d94b3 100644 --- a/numpy/doc/subclassing.py +++ b/numpy/doc/subclassing.py @@ -562,7 +562,7 @@ pass on to ``A.__array_ufunc__``, the ``super`` call in ``A`` would go to Prior to numpy 1.13, the behaviour of ufuncs could only be tuned using ``__array_wrap__`` and ``__array_prepare__``. These two allowed one to -change the output type of a ufunc, but, in constrast to +change the output type of a ufunc, but, in contrast to ``__array_ufunc__``, did not allow one to make any changes to the inputs. It is hoped to eventually deprecate these, but ``__array_wrap__`` is also used by other numpy functions and methods, such as ``squeeze``, so at the |