[Numpy-discussion] __array_function related regression for 1.17.0rc1

[Ralf Gommers]

On Mon, Jul 1, 2019 at 6:08 AM Juan Nunez-Iglesias <jni at fastmail.com> wrote:

> Hi Chuck, and thanks for putting this together!
>
> It seems the release has broken existing uses of dask array with `np.min`
> (I presume among other functions):
>
> https://github.com/dask/dask/issues/5031
>
> Perhaps `__array_function__` should be switched off for one more release
> cycle? I imagine that scikit-image [1] are not the only ones using this
> construct, which worked fine before `__array_function__`.
>

Hmm, I'd really like to avoid that, that would be another 6 months where we
get close to zero testing.

This issue is not very surprising - __array_function__ is going to have a
fair bit of backwards compat impact for people who were relying on feeding
all sorts of stuff into numpy functions that previously got converted with
asarray. At this point Dask is the main worry, followed by CuPy and
pydata/sparse. All those libraries have very responsive maintainers.
Perhaps we should just try to get these issues fixed asap in those
libraries instead?

Cheers,
Ralf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190701/2f5e2597/attachment.html>