[Numpy-discussion] NEP: Dispatch Mechanism for NumPy’s high level API (original) (raw)
Marten van Kerkwijk m.h.vankerkwijk at gmail.com
Tue Jun 5 15:33:40 EDT 2018
- Previous message (by thread): [Numpy-discussion] NEP: Dispatch Mechanism for NumPy’s high level API
- Next message (by thread): [Numpy-discussion] NEP: Dispatch Mechanism for NumPy’s high level API
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Stephan,
Things would, I think, make much more sense if ndarray.__array_ufunc__
(or *_function__
) actually were the implementation for array-only. But
while that is something I'd like to eventually get to, it seems out of
scope for the current discussion. But we should be sure that the ndarray
versions return either NotImplemented
or a result.
Given that, I think that perhaps it is also best not to do
NotImplementedButCoercible
- as I think the implementers of
__array_function__
perhaps should just do that themselves. But I may well
swing the other way again... Good examples of non-trivial benefits would
help.
All the best,
Marten -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20180605/7aac7d2c/attachment.html>
- Previous message (by thread): [Numpy-discussion] NEP: Dispatch Mechanism for NumPy’s high level API
- Next message (by thread): [Numpy-discussion] NEP: Dispatch Mechanism for NumPy’s high level API
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]