On Fri, Jul 4, 2014 at 9:02 PM, Ralf Gommers <ralf.gomm...@gmail.com> wrote: > > On Fri, Jul 4, 2014 at 10:00 PM, Charles R Harris > <charlesr.har...@gmail.com> wrote: >> >> On Fri, Jul 4, 2014 at 1:42 PM, Charles R Harris >> <charlesr.har...@gmail.com> wrote: >>> >>> 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? > > > It depends how bad the break is, but in principle I'd say that breaking > Matplotlib is not OK.
I agree. If it's easy to hack around it and issue a warning for now, and doesn't have other negative consequences, then IMO we should give matplotlib a release or so worth of grace period to fix things. -n -- Nathaniel J. Smith Postdoctoral researcher - Informatics - University of Edinburgh http://vorpus.org _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
