[Numpy-discussion] Extent to which to work around matrix and other duck/subclass limitations

[Marten van Kerkwijk]

> In a way, I brought it up mostly as a concrete example of an internal
> implementation which we cannot change to an objectively cleaner one because
> other packages rely on an out-of-date numpy API.
>
> Should have added: rely on an out-of-date numpy API where we have multiple
ways for packages to provide their own overrides. But I guess in this case
it is really matrix which is the problem. If so, maybe just adding kwargs
to it is something we should consider.

-- Marten
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20190611/8a0c1289/attachment.html>