8000 ENH: Implement concatenate dtype and casting keyword arguments by seberg · Pull Request #16134 · numpy/numpy · GitHub
[go: up one dir, main page]

Skip to content

ENH: Implement concatenate dtype and casting keyword arguments #16134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Sep 3, 2020
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update doc/release/upcoming_changes/16134.compatibility.rst
Co-authored-by: Matti Picus <matti.picus@gmail.com>
  • Loading branch information
seberg and mattip authored Sep 3, 2020
commit 1a79c064ff65a150c18d8c2ad3050350532f1b0e
10 changes: 5 additions & 5 deletions doc/release/upcoming_changes/16134.compatibility.rst
Original file line number Diff line number Diff line change
@@ -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.
0