diff options
| author | Loïc Estève <loic.esteve@ymail.com> | 2016-03-10 19:37:16 +0100 |
|---|---|---|
| committer | Loïc Estève <loic.esteve@ymail.com> | 2016-04-04 09:57:10 +0200 |
| commit | 8f27d12f5f8f4c8acd3e902bed818663ab48a646 (patch) | |
| tree | 282ddc22325965ae129dab9ebcec847e02500ad2 /doc | |
| parent | 25d60a989766e630b92a79284388845ade96d3d0 (diff) | |
| download | numpy-8f27d12f5f8f4c8acd3e902bed818663ab48a646.tar.gz | |
FIX ufunc called on memmap return a ndarray
Special case for reduction functions (e.g. np.sum with axis=None) that
return a numpy scalar.
Keep original memmap subclasses behavior to be on the safe side.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/release/1.12.0-notes.rst | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/release/1.12.0-notes.rst b/doc/release/1.12.0-notes.rst index 058bdaac7..41d15d114 100644 --- a/doc/release/1.12.0-notes.rst +++ b/doc/release/1.12.0-notes.rst @@ -177,6 +177,13 @@ were doing. This caused a complication in the downstream 'pandas' library that encountered an issue with 'numpy' compatibility. Now, all array-like methods in this module are called with keyword arguments instead. +Operations on np.memmap objects return numpy arrays in most cases +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Previously operations on a memmap (e.g. adding 1 to it) object would +misleadingly return a memmap instance even if the result was actually +not memmapped. Also reduction of a memmap (e.g. ``.sum(axis=None``) +return a numpy scalar instead of a 0d memmap. + Deprecations ============ |