diff options
author | Sebastian Berg <sebastian@sipsolutions.net> | 2020-09-03 10:16:55 -0500 |
---|---|---|
committer | GitHub <noreply@github.com> | 2020-09-03 10:16:55 -0500 |
commit | 1a79c064ff65a150c18d8c2ad3050350532f1b0e (patch) | |
tree | 620c5aea863a05aebce12043d87b988fafcb76b3 | |
parent | 3c746b0f60471e20627588c752dd68ad962fb33d (diff) | |
download | numpy-1a79c064ff65a150c18d8c2ad3050350532f1b0e.tar.gz |
Update doc/release/upcoming_changes/16134.compatibility.rst
Co-authored-by: Matti Picus <matti.picus@gmail.com>
-rw-r--r-- | doc/release/upcoming_changes/16134.compatibility.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/release/upcoming_changes/16134.compatibility.rst b/doc/release/upcoming_changes/16134.compatibility.rst index 4270ea271..373cecec0 100644 --- a/doc/release/upcoming_changes/16134.compatibility.rst +++ b/doc/release/upcoming_changes/16134.compatibility.rst @@ -1,8 +1,8 @@ Same kind casting in concatenate with ``axis=None`` --------------------------------------------------- -Unlike most `~numpy.concatenate` calls, when no axis -was given (the ravelled arrays being concatenated) -previously "unsafe" casting was used. -This is now deprecated and "same kind" casting will be -used by default. The new ``casting`` keyword argument +When `~numpy.concatenate` is called with `axis=None`, +the flattened arrays were cast with ``unsafe``. Any other axis +choice uses "same kind". That different default +has been deprecated and "same kind" casting will be used +instead. The new ``casting`` keyword argument can be used to retain the old behaviour. |