[Numpy-discussion] NEP: Dispatch Mechanism for NumPy’s high level API

Hameer Abbasi einstein.edison at gmail.com
Wed Jun 6 06:20:03 EDT 2018

On 6. Jun 2018 at 05:41, Nathan Goldbaum <nathan12343 at gmail.com> wrote:

Oh wait, since the decorated version of the ufunc will be the one in the
public numpy API it won't break. It would only break if the callable that
was passed in *wasn't* the decorated version, so it kinda *has* to pass in
the decorated function to preserve backward compatibility. Apologies for
the noise.

On Tue, Jun 5, 2018 at 7:39 PM, Nathan Goldbaum <nathan12343 at gmail.com>

> Hmm, does this mean the callable that gets passed into __array_ufunc__
> will change? I'm pretty sure that will break the dispatch mechanism I'm
> using in my __array_ufunc__ implementation, which directly checks whether
> the callable is in one of several tuples of functions that have different
> behavior.

Section “Non-Goals” states that Ufuncs will not be part of this protocol,
__array_ufunc__ will be used to override those as usual.

Sent from Astro <https://www.helloastro.com> for Mac
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20180606/30d75520/attachment-0001.html>

More information about the NumPy-Discussion mailing list