[Numpy-discussion] Questions about fixes for 1.9.0rc2

Charles R Harris charlesr.harris at gmail.com
Fri Jul 4 15:42:41 EDT 2014


Sebastian Seberg has fixed one class of test failures due to the indexing
changes in numpy 1.9.0b1.  There are some remaining errors, and in the case
of the Matplotlib failures, they look to me to be Matplotlib bugs. The 2-d
arrays that cause the error are returned by the overloaded
_interpolate_single_key function in CubicTriInterpolator that is documented
in the base class to return a 1-d array, whereas the actual dimensions are
of the form (n, 1). The question is, what is the best work around here for
these sorts errors? Can we afford to break Matplotlib and other packages on
account of a bug that was previously accepted by Numpy? Perhaps a
FutureWarning rather than an error would be more appropriate at this point,
and that modification would be easy to make.

Thoughts?

Chuck
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20140704/f7295592/attachment.html>


More information about the NumPy-Discussion mailing list