diff options
| author | Eric Wieser <wieser.eric@gmail.com> | 2019-05-26 12:57:36 -0700 |
|---|---|---|
| committer | Eric Wieser <wieser.eric@gmail.com> | 2019-06-04 22:35:10 -0700 |
| commit | f427b610b2f63dd43d9a2584944fa3265249e694 (patch) | |
| tree | b3714c0fde6fdf18e509e14557cf9aad67de9bf4 /numpy/lib/nanfunctions.py | |
| parent | d3c1c222292725d13190f73e23ec49e7b10e86cf (diff) | |
| download | numpy-f427b610b2f63dd43d9a2584944fa3265249e694.tar.gz | |
DEP: Deprecate nonzero(0d) in favor of calling atleast_1d explicitly
This is a weird enough corner case that either:
* No one is running into it, and downstream code is broken on 0d arrays anyway
* People already have hacks in place to work around it:
* Calling `nonzero` but handling the result specially if the array was 0d. We want to dissuade this in case we change the result of nonzero to be better in future.
* Not calling `nonzero` at all if the array is zerod (such as by using `atleast1d`). These users are unaffected.
Diffstat (limited to 'numpy/lib/nanfunctions.py')
0 files changed, 0 insertions, 0 deletions