[Numpy-discussion] Polynomial silent breakage with 1.13
wieser.eric+numpy at gmail.com
Fri Jul 7 13:14:25 EDT 2017
That’s a regression, and it’s on me, in 8762.
That was a side effect of a fix for the weird behaviour here
I think we need to fix this in 1.13.2, so we should file an issue about it.
On Fri, 7 Jul 2017 at 18:31 Matthew Brett <matthew.brett at gmail.com> wrote:
> Our (nipy's) test suite just failed with the upgrade to numpy 1.13,
> and the cause boiled down to this:
> import numpy as np
> poly = np.poly1d()
> poly.c *= 2
> Numpy 1.12 gives (to me) expected output:
> Numpy 1.13 gives (to me) unexpected output:
> The problem is caused by the fact that the coefficients are now a
> *copy* of the actual coefficient array - I think in an attempt to stop
> us modifying the coefficients directly.
> I can't see any deprecation warnings with `-W always`.
> The pain point here is that code that used to give the right answer
> has now (I believe silently) switched to giving the wrong answer.
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion