From 1a79c064ff65a150c18d8c2ad3050350532f1b0e Mon Sep 17 00:00:00 2001 From: Sebastian Berg Date: Thu, 3 Sep 2020 10:16:55 -0500 Subject: Update doc/release/upcoming_changes/16134.compatibility.rst Co-authored-by: Matti Picus --- doc/release/upcoming_changes/16134.compatibility.rst | 10 +++++----- 1 file 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. -- cgit v1.2.1