diff options
| author | Matti Picus <matti.picus@gmail.com> | 2020-03-31 23:22:01 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-03-31 23:22:01 +0300 |
| commit | 642181c76b11bd1cc87ee7443d3ee215744df0fd (patch) | |
| tree | ff83018220f879b7dbc65644f096f3c0fe698a83 /doc | |
| parent | 5d8bcae56a337d21d7bf60d042c7dff32d91b451 (diff) | |
| parent | b88415edf288cff6ab89b19bb7f7ca55ec1e6ade (diff) | |
| download | numpy-642181c76b11bd1cc87ee7443d3ee215744df0fd.tar.gz | |
Merge pull request #15882 from eric-wieser/reject-illegal-strides-in-ndarray.__new__
BUG: Do not ignore empty tuple of strides in ndarray.__new__
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. |