diff options
| author | Alexander Belopolsky <abalkin@users.noreply.github.com> | 2020-08-03 11:00:58 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-08-03 10:00:58 -0500 |
| commit | 333e08eced6ccabd8ea6e4f6320f00187f9585c5 (patch) | |
| tree | f7865fc7e2f8dba5f01f869c1b6b73615a2e3e8c /doc/release | |
| parent | 5b5a74043985b5cf577cd14b9a326b8eeb13c11a (diff) | |
| download | numpy-333e08eced6ccabd8ea6e4f6320f00187f9585c5.tar.gz | |
BUG: Set readonly flag in array interface instead of warning (gh-16350)
Set readonly flags in array interface dict and array struct
capsule returned by an array with warn_on_write flag set
instead of producing a deprecation warning.
Closes #16335
Diffstat (limited to 'doc/release')
| -rw-r--r-- | doc/release/upcoming_changes/16350.compatibility.rst | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/release/upcoming_changes/16350.compatibility.rst b/doc/release/upcoming_changes/16350.compatibility.rst new file mode 100644 index 000000000..67673a6b1 --- /dev/null +++ b/doc/release/upcoming_changes/16350.compatibility.rst @@ -0,0 +1,8 @@ +Writing to the result of `numpy.broadcast_arrays` will export readonly buffers +------------------------------------------------------------------------------ + +In NumPy 1.17 `numpy.broadcast_arrays` started warning when the resulting array +was written to. This warning was skipped when the array was used through the +buffer interface (e.g. ``memoryview(arr)``). The same thing will now occur for the +two protocols ``__array_interface__``, and ``__array_struct__`` returning read-only +buffers instead of giving a warning.
\ No newline at end of file |