diff options
| author | ahaldane <ealloc@gmail.com> | 2016-04-04 13:10:40 -0400 |
|---|---|---|
| committer | ahaldane <ealloc@gmail.com> | 2016-04-04 13:10:40 -0400 |
| commit | 2fb95995d402cd065f83e72d596bfdf17be9ea57 (patch) | |
| tree | fd4dd6340843b9257b14c49066027383f897e835 /doc | |
| parent | 6ab89b8c66f68dfac9fde6eab843990a732a9a27 (diff) | |
| parent | 8f27d12f5f8f4c8acd3e902bed818663ab48a646 (diff) | |
| download | numpy-2fb95995d402cd065f83e72d596bfdf17be9ea57.tar.gz | |
Merge pull request #7406 from lesteve/memmap-ufunc-return-ndarray
ENH ufunc called on memmap return a ndarray
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 486759494..b9e405154 100644 --- a/doc/release/1.12.0-notes.rst +++ b/doc/release/1.12.0-notes.rst @@ -181,6 +181,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 ============ |