diff options
author | Stephan Hoyer <shoyer@google.com> | 2019-05-26 16:12:26 -0700 |
---|---|---|
committer | Stephan Hoyer <shoyer@google.com> | 2019-05-26 16:12:26 -0700 |
commit | 5e8a4a11a900d9427368fe1f10c8086290ff01f1 (patch) | |
tree | 9eb6358ef5a85c1479de5f3ed6f00f60c3e39762 /numpy/doc/basics.py | |
parent | 849e4d429951ad93691e6149d070b9d31536cc12 (diff) | |
download | numpy-5e8a4a11a900d9427368fe1f10c8086290ff01f1.tar.gz |
DOC: caution against relying upon NumPy's implementation in subclasses
I think this is an important warning to include for subclass authors.
Otherwise, we will be expanding our exposure of internal APIs as part of
``__array_function__``. All things being equal, it's great when things "just
work" subclasses, but I don't want to guarantee it. In particular, I would be
very displeased if ``__array_function__`` leads to NumPy adding more subclass
specific hacks like always calling ``mean()`` inside ``median()`` (GH-3846).
mhvk: please take a look.
Diffstat (limited to 'numpy/doc/basics.py')
0 files changed, 0 insertions, 0 deletions