On 6. Jun 2018 at 05:41, Nathan Goldbaum <nathan12...@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 <nathan12...@gmail.com> wrote: > 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
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
