summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorCharles Harris <charlesr.harris@gmail.com>2013-05-02 19:40:38 -0700
committerCharles Harris <charlesr.harris@gmail.com>2013-05-02 19:40:38 -0700
commit8fa264a98158f0c3c8a99061f64f954fc59094a4 (patch)
treec4d298333a826f45c4fbb9a7fcfe9e9a6abe3ab7 /doc
parent0330caed36ab77309f367c7b67c878452b7e5dd0 (diff)
parent6b0784b11f422f9148d01f01cfba09a5dcb0cd4a (diff)
downloadnumpy-8fa264a98158f0c3c8a99061f64f954fc59094a4.tar.gz
Merge pull request #2822 from ContinuumIO/custom_output_operand_fix
Fix for ufuncs with built in input operands and custom output operands
Diffstat (limited to 'doc')
-rw-r--r--doc/release/1.8.0-notes.rst8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/release/1.8.0-notes.rst b/doc/release/1.8.0-notes.rst
index 95bad26cc..c5c9d6e8d 100644
--- a/doc/release/1.8.0-notes.rst
+++ b/doc/release/1.8.0-notes.rst
@@ -113,6 +113,14 @@ causes the returned array to be inverted.
C-API
~~~~~
+New ufuncs can now be registered with built in input types and a custom
+output type. Before this change, NumPy wouldn't be able to find the right
+ufunc loop function when the ufunc was called from Python, because the ufunc
+loop signature matching logic wasn't looking at the output operand type.
+Now the correct ufunc loop is found, as long as the user provides an output
+argument with the correct output type.
+
+
Changes
=======