diff options
| author | Eric Wieser <wieser.eric@gmail.com> | 2020-03-31 17:58:15 +0100 |
|---|---|---|
| committer | Eric Wieser <wieser.eric@gmail.com> | 2020-03-31 20:48:06 +0100 |
| commit | b88415edf288cff6ab89b19bb7f7ca55ec1e6ade (patch) | |
| tree | f16c38708ba9bdf057b0932d5529a3f10654cdfa /doc | |
| parent | b570f73d39505926478fda1b1a496ac3e707d33d (diff) | |
| download | numpy-b88415edf288cff6ab89b19bb7f7ca55ec1e6ade.tar.gz | |
BUG: Do not ignore empty tuple of strides in ndarray.__new__
Previously this was treated as though an empty set of strides were passed.
Now this is treated as a request for `.strides == ()`.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/release/upcoming_changes/15882.compatibility.rst | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/release/upcoming_changes/15882.compatibility.rst b/doc/release/upcoming_changes/15882.compatibility.rst new file mode 100644 index 000000000..5790c081c --- /dev/null +++ b/doc/release/upcoming_changes/15882.compatibility.rst @@ -0,0 +1,5 @@ +The ``numpy.ndarray`` constructor no longer interprets ``strides=()`` as ``strides=None`` +----------------------------------------------------------------------------------------- +The former has changed to have the expected meaning of setting +`numpy.ndarray.strides` to ``()``, while the latter continues to result in +strides being chosen automatically. |