From 900d82ecd42932fc62c080341f8c918c9e1125b7 Mon Sep 17 00:00:00 2001 From: Mark Wiebe Date: Wed, 31 Aug 2011 11:42:02 -0700 Subject: DOC: Add note about .reduce evaluation order --- doc/release/2.0.0-notes.rst | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'doc') diff --git a/doc/release/2.0.0-notes.rst b/doc/release/2.0.0-notes.rst index 169869bc5..daec1013f 100644 --- a/doc/release/2.0.0-notes.rst +++ b/doc/release/2.0.0-notes.rst @@ -110,6 +110,12 @@ functions more consistent with NumPy's general approach of taking views where possible, and performs much faster as well. This has the potential to break code that assumes a copy is made instead of a view. +The .reduce functions evaluates some reductions in a different +order than in previous versions of NumPy, generally providing higher +performance. Because of the nature of floating-point arithmetic, this +may subtly change some results, just as linking NumPy to a different +BLAS implementations such as MKL can. + The function np.concatenate tries to match the layout of its input arrays. Previously, the layout did not follow any particular reason, and depended in an undesirable way on the particular axis chosen for -- cgit v1.2.1