diff options
| author | melissawm <melissawm.github@gmail.com> | 2021-12-09 14:52:21 -0300 |
|---|---|---|
| committer | melissawm <melissawm.github@gmail.com> | 2021-12-09 14:52:21 -0300 |
| commit | bd6ea9b9f5c62e9546235039cf6fa15d854cb464 (patch) | |
| tree | e317f54532528a3e6f4b8eadf58d6c1793b26cdf | |
| parent | e06f12722c23552fb06ea8d5927d3891e898d94d (diff) | |
| download | numpy-bd6ea9b9f5c62e9546235039cf6fa15d854cb464.tar.gz | |
DOC: fix link to numpy-discussion
| -rw-r--r-- | doc/neps/nep-0031-uarray.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/neps/nep-0031-uarray.rst b/doc/neps/nep-0031-uarray.rst index fa06fc022..b746c267d 100644 --- a/doc/neps/nep-0031-uarray.rst +++ b/doc/neps/nep-0031-uarray.rst @@ -302,7 +302,7 @@ This is different from monkeypatching in a few different ways: so there is at least the loose sense of an API contract. Monkeypatching does not provide this ability. * There is the ability of locally switching the backend. -* It has been `suggested <https://mail.python.org/archives/list/numpy-discussion@python.org/thread/X3IJH4M4YUYRF6N5XZKL7XT6OBJ2U2EA/#RJQXTDWXWGVX3XIKDJI7BYP2X2OIE632>`_ +* It has been `suggested <https://mail.python.org/archives/list/numpy-discussion@python.org/message/PS7EN3CRT6XERNTCN56MAYOXFFFEC55G/>`_ that the reason that 1.17 hasn't landed in the Anaconda defaults channel is due to the incompatibility between monkeypatching and ``__array_function__``, as monkeypatching would bypass the protocol completely. |