diff options
author | Sebastian Berg <sebastian@sipsolutions.net> | 2021-06-07 13:17:45 -0500 |
---|---|---|
committer | Sebastian Berg <sebastian@sipsolutions.net> | 2021-06-07 13:32:07 -0500 |
commit | cbd0c97bf8ca5148f581c644968b6eb4b11df40d (patch) | |
tree | a24a2dc114f6e80b259671dddf9fa90e25d04524 /numpy/core | |
parent | 6790873334b143117f4e8d1f515def8c7fdeb9fb (diff) | |
download | numpy-cbd0c97bf8ca5148f581c644968b6eb4b11df40d.tar.gz |
NEP: Accept NEP 35 as final
This accepts NEP 35 as final. There has been no discussion about it
in a long time. The current mode is strict about type input
(`like=` must be an array-like). So that most of the "open" points
are OK to remain open.
Unless we need to discuss the name `like` or the fact that we pass
an array-like itself, the previously noted open points gh-17075
all seem not very relevant anymore.
Diffstat (limited to 'numpy/core')
-rw-r--r-- | numpy/core/overrides.py | 6 |
1 files changed, 1 insertions, 5 deletions
diff --git a/numpy/core/overrides.py b/numpy/core/overrides.py index c2b5fb7fa..70085d896 100644 --- a/numpy/core/overrides.py +++ b/numpy/core/overrides.py @@ -18,11 +18,7 @@ array_function_like_doc = ( NumPy arrays. If an array-like passed in as ``like`` supports the ``__array_function__`` protocol, the result will be defined by it. In this case, it ensures the creation of an array object - compatible with that passed in via this argument. - - .. note:: - The ``like`` keyword is an experimental feature pending on - acceptance of :ref:`NEP 35 <NEP35>`.""" + compatible with that passed in via this argument.""" ) def set_array_function_like_doc(public_api): |