Hi! > On Friday, Oct 19, 2018 at 6:09 PM, Stephan Hoyer <[email protected] > (mailto:[email protected])> wrote: > I don't think it makes much sense to change NumPy's existing usage of > asarray() to asanyarray() unless we add subok=True arguments (which default > to False). But this ends up cluttering NumPy's public API, which is also > undesirable. > Agreed so far. > > The preferred way to override NumPy functions going forward should be > __array_function__. >
I think we should “soft support” i.e. allow but consider unsupported, the case where one of NumPy’s functions is implemented in terms of others and “passing through” an array results in the correct behaviour for that array. > > On Fri, Oct 19, 2018 at 8:13 AM Marten van Kerkwijk > <[email protected] (mailto:[email protected])> wrote: > > There are exceptions for `matrix` in quite a few places, and there now is > > warning for `maxtrix` - it might not be bad to use `asanyarray` and add an > > exception for `maxtrix`. Indeed, I quite like the suggestion by Eric Wieser > > to just add the exception to `asanyarray` itself - that way when matrix is > > truly deprecated, it will be a very easy change. > > > > -- Marten > > _______________________________________________ > > NumPy-Discussion mailing list > > [email protected] (mailto:[email protected]) > > https://mail.python.org/mailman/listinfo/numpy-discussion > _______________________________________________ > NumPy-Discussion mailing list > [email protected] > https://mail.python.org/mailman/listinfo/numpy-discussion Best Regards, Hameer Abbasi
_______________________________________________ NumPy-Discussion mailing list [email protected] https://mail.python.org/mailman/listinfo/numpy-discussion
