summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStephan Hoyer <shoyer@google.com>2018-10-14 13:44:41 -0700
committerStephan Hoyer <shoyer@google.com>2018-10-14 13:45:17 -0700
commit79b47c0983a09773150e37b49d7bdfb3761ade03 (patch)
tree0f6a8832c26383c732099be2bd8a6618b01673c8
parent18c12106b1c59052ab9c94a5a67513120580a10b (diff)
downloadnumpy-79b47c0983a09773150e37b49d7bdfb3761ade03.tar.gz
NEP: add notes about updates to NEP-18
As discussion in GH12140
-rw-r--r--doc/neps/nep-0018-array-function-protocol.rst7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/neps/nep-0018-array-function-protocol.rst b/doc/neps/nep-0018-array-function-protocol.rst
index 210021d99..b3ad6aaf8 100644
--- a/doc/neps/nep-0018-array-function-protocol.rst
+++ b/doc/neps/nep-0018-array-function-protocol.rst
@@ -298,7 +298,7 @@ and this ensures that checking overloads has acceptable performance even when
there are a large number of overloaded arguments. To avoid long-term divergence
between these two dispatch protocols, we should
`also update <https://github.com/numpy/numpy/issues/11306>`_
-``__array_ufunc__`` to match this behavior.
+``__array_ufunc__`` to match this behavior (update: this has happened).
Special handling of ``numpy.ndarray``
'''''''''''''''''''''''''''''''''''''
@@ -403,6 +403,11 @@ from a tuple ``*args`` and dict ``**kwargs``.) This shouldn't stop us from
writing overrides for functions with non-generic signatures that can't use the
decorator, but we should consider these cases carefully.
+.. note::
+
+ The code for ``array_function_dispatch`` above has been updated from the
+ original version of this NEP to match the actual implementation in NumPy.
+
Extensibility
~~~~~~~~~~~~~