[Numpy-discussion] Adding to the non-dispatched implementation of NumPy methods

Stephan Hoyer shoyer at gmail.com
Fri Apr 26 21:26:24 EDT 2019

On Fri, Apr 26, 2019 at 9:16 AM Hameer Abbasi <einstein.edison at gmail.com>

> That said, please save it a separate discussion thread, given that the
> design of uarray is (wisely) orthogonal to NEP-18.
> I disagree, I don’t consider it orthogonal: I’m presenting a way to avoid
> the very protocols being discussed, and I’d like to avoid duplicate work,
> or making NumPy itself un-maintainable. Please note the text of NEP-18:
> The __array_function__protocol, and its use on particular functions, is
> *experimental*. We plan to retain an interface that makes it possible to
> override NumPy functions, but the way to do so for particular functions *can
> and will change *with little warning. If such reduced backwards
> compatibility guarantees are not accepted to you, do not rely upon
> overrides of NumPy functions for non-NumPy arrays. See “Non-goals” below
> for more details.
> What I’m presenting is within scope, as it’s an alternative method.
> Best Regards,
> Hameer Abbasi

Are there aspects of your uarray proposal that are relevant to the current
proposed revisions to NEP 18? If so, please restate them :).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190426/44359b87/attachment.html>

More information about the NumPy-Discussion mailing list