summaryrefslogtreecommitdiff
path: root/doc/release
diff options
context:
space:
mode:
authorMark Wiebe <mwwiebe@gmail.com>2011-08-31 11:42:02 -0700
committerMark Wiebe <mwwiebe@gmail.com>2011-08-31 11:42:02 -0700
commit900d82ecd42932fc62c080341f8c918c9e1125b7 (patch)
tree95f078a712a086abb76e2d357e4fa6261c8145d5 /doc/release
parent98ccad69e870ac35c20f0130586c70448d315134 (diff)
downloadnumpy-900d82ecd42932fc62c080341f8c918c9e1125b7.tar.gz
DOC: Add note about <ufunc>.reduce evaluation order
Diffstat (limited to 'doc/release')
-rw-r--r--doc/release/2.0.0-notes.rst6
1 files changed, 6 insertions, 0 deletions
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 <ufunc>.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