diff options
| author | Matti Picus <matti.picus@gmail.com> | 2019-06-28 18:27:42 -0700 |
|---|---|---|
| committer | Sebastian Berg <sebastian@sipsolutions.net> | 2019-06-28 18:27:42 -0700 |
| commit | 59ebfbbe32bcac4a278c39a9a24b80a42d47a8f6 (patch) | |
| tree | abcdbeac29cc19a7bb839ab4578a08668e6eaef5 /numpy/array_api/tests/test_array_object.py | |
| parent | e7383b5d5dff636ed92667a28751ce18f7086097 (diff) | |
| download | numpy-59ebfbbe32bcac4a278c39a9a24b80a42d47a8f6.tar.gz | |
ENH: Deprecate writeable broadcast_array (#12609)
When the base is not an array (or generally when the flag of the base
array was toggled), it is OK to allow setting the writeable flag to
True, as long as any ancestor (especially the last one) is writeable.
This commit also slightly change the behaviour of the base attribute.
---
* ENH: Deprecate writeable broadcast_array
* ENH: Make writeable flag enabling more reliable for non-array bases
When the base is not an array (or generally when the flag of the base
array was toggled), it is OK to allow setting the writeable flag to
True, as long as any ancestor (especially the last one) is writeable.
* Update doc/release/1.17.0-notes.rst
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
* Update doc/release/1.17.0-notes.rst
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
* Update numpy/lib/tests/test_stride_tricks.py
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
* Update numpy/core/tests/test_multiarray.py
Co-Authored-By: Sebastian Berg <sebastian@sipsolutions.net>
* DOC: improve warning (from review)
Diffstat (limited to 'numpy/array_api/tests/test_array_object.py')
0 files changed, 0 insertions, 0 deletions