Re: [Numpy-discussion] Polynomial silent breakage with 1.13

I've gone ahead and filed one at https://github.com/numpy/numpy/issues/9385, along with links to relevant PRs. On Fri, 7 Jul 2017 at 22:28 Matthew Brett wrote: > Hi, > > On Fri, Jul 7, 2017 at 6:14 PM, Eric Wieser > wrote: > > That’s a regression, and it’s on me, in 8762. > > > > That was a sid

Re: [Numpy-discussion] Polynomial silent breakage with 1.13

Hi, On Fri, Jul 7, 2017 at 6:14 PM, Eric Wieser wrote: > 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. Thanks for the feedback. Do you want to file a

Re: [Numpy-discussion] Polynomial silent breakage with 1.13

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. Eric ​ On Fri, 7 Jul 2017 at 18:31 Matthew Br

[Numpy-discussion] Polynomial silent breakage with 1.13

Hi, 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([1]) poly.c[0] *= 2 print(poly.c) ``` Numpy 1.12 gives (to me) expected output: [2] Numpy 1.13 gives (to me) unexpected output: [1] The problem