From f6861923209df65d9c4253368061072eda67ea77 Mon Sep 17 00:00:00 2001 From: Charles Harris Date: Fri, 19 Jun 2015 17:31:35 -0600 Subject: DEP,MAINT: Raise IndexError if axis != 0 when concatenating 1-D arrays. This was deprecated in NumPy 1.7 with a warning that it would raise an error in the future. Tests for the new error are added and the test that allowed that special case is removed. --- doc/release/1.10.0-notes.rst | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'doc') diff --git a/doc/release/1.10.0-notes.rst b/doc/release/1.10.0-notes.rst index ed33cc9e3..d3b99cf76 100644 --- a/doc/release/1.10.0-notes.rst +++ b/doc/release/1.10.0-notes.rst @@ -52,6 +52,11 @@ relaxed stride checking ~~~~~~~~~~~~~~~~~~~~~~~ NPY_RELAXED_STRIDE_CHECKING is now true by default. +Concatenation of 1d arrays along any but ``axis=0`` raises ``IndexError`` +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +Using axis != 0 has raised a DeprecationWarning since NumPy 1.7, it now +raises an error. + *np.ravel*, *np.diagonal* and *np.diag* now preserve subtypes ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ There was inconsistent behavior between *x.ravel()* and *np.ravel(x)*, as @@ -76,6 +81,9 @@ which now returns a view in all cases. The dtype structure (PyArray_Descr) has a new member at the end to cache its hash value. This shouldn't affect any well-written applications. +The change to the concatenation function DeprecationWarning also affects +PyArray_ConcatenateArrays, + recarray field return types ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Previously the returned types for recarray fields accessed by attribute and by -- cgit v1.2.1