diff options
author | Allan Haldane <allan.haldane@gmail.com> | 2016-03-19 15:29:59 -0400 |
---|---|---|
committer | Allan Haldane <allan.haldane@gmail.com> | 2016-06-14 00:46:42 -0400 |
commit | 59173726d78e5d9a2ab117bc57961e941769424b (patch) | |
tree | b0fc226e8e2a0a197a8bcfefc3cca0063c95071c /doc | |
parent | a94fd6122aa30b2cf24757c3e3e826d532c7fe6c (diff) | |
download | numpy-59173726d78e5d9a2ab117bc57961e941769424b.tar.gz |
MAINT: FutureWarning for changes to np.average subclass handling
Fixes #7403
Diffstat (limited to 'doc')
-rw-r--r-- | doc/release/1.12.0-notes.rst | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/release/1.12.0-notes.rst b/doc/release/1.12.0-notes.rst index aaa62e2ac..15f22700c 100644 --- a/doc/release/1.12.0-notes.rst +++ b/doc/release/1.12.0-notes.rst @@ -18,6 +18,9 @@ Future Changes * In 1.13 NAT will always compare False except for ``NAT != NAT``, which will be True. In short, NAT will behave like NaN +* In 1.13 np.average will preserve subclasses, to match the behavior of most + other numpy functions such as np.mean. In particular, this means calls which + returned a scalar may return a 0-d subclass object instead. Compatibility notes @@ -86,6 +89,9 @@ FutureWarning to changed behavior * ``np.full`` now returns an array of the fill-value's dtype if no dtype is given, instead of defaulting to float. +* np.average will emit a warning if the argument is a subclass of ndarray, + as the subclass will be preserved starting in 1.13. (see Future Changes) + C API ~~~~~ |