summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorCharles Harris <charlesr.harris@gmail.com>2016-11-02 16:47:48 -0600
committerCharles Harris <charlesr.harris@gmail.com>2016-11-02 18:02:02 -0600
commitaf32cce15d670ff479c46b8580116619e29261ca (patch)
treea1053c28276bbb7a13947a300cf1b3761363dcd6 /doc
parent9451faa445571cf1839e415bb419afa18c0e7ed9 (diff)
downloadnumpy-af32cce15d670ff479c46b8580116619e29261ca.tar.gz
DOC: Mention the fpower function in the 1.12.0 release notes.
[ci skip]
Diffstat (limited to 'doc')
-rw-r--r--doc/release/1.12.0-notes.rst9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/release/1.12.0-notes.rst b/doc/release/1.12.0-notes.rst
index 0baa33049..3630a735c 100644
--- a/doc/release/1.12.0-notes.rst
+++ b/doc/release/1.12.0-notes.rst
@@ -261,6 +261,15 @@ values. There are two different propagation modes. The default causes masked
values to contaminate the result with masks, but the other mode only outputs
masks if there is no alternative.
+New ``float_power`` ufunc
+~~~~~~~~~~~~~~~~~~~~~~~~~
+The new ``float_power`` ufunc is like the ``power`` function except all
+computation is done in a minimum precision of float64. There was a long
+discussion on the numpy mailing list of how to treat integers to negative
+integer powers and a popular proposal was that the ``__pow__`` operator should
+always return results of at least float64 precision. The ``float_power``
+function implements that option. Note that it does not support object arrays.
+
Improvements
============