Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-07 Thread Ryan May
On Fri, Jul 7, 2017 at 4:27 PM, Marten van Kerkwijk < m.h.vankerkw...@gmail.com> wrote: > Hi All, > > I doubt I'm really the last one thinking ndarray subclassing is a good > idea, but as that was stated, I feel I should at least pipe in. It > seems to me there is both a perceived problem -- with

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

2017-07-07 Thread Marten van Kerkwijk
Hi All, I doubt I'm really the last one thinking ndarray subclassing is a good idea, but as that was stated, I feel I should at least pipe in. It seems to me there is both a perceived problem -- with the two subclasses that numpy provides -- `matrix` and `MaskedArray` -- both being problematic in

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

2017-07-07 Thread Eric Wieser
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

2017-07-07 Thread Matthew Brett
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

2017-07-07 Thread Eric Wieser
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

2017-07-07 Thread Matthew Brett
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

Re: [Numpy-discussion] record data previous to Numpy use

2017-07-07 Thread Derek Homeier
On 07 Jul 2017, at 4:24 PM, paul.carr...@free.fr wrote: > > ps : I'd like to use the following code that is much more familiar for me :-) > > COMP_list = np.asarray(COMP_list, dtype = np.float64) > i = np.arange(1,NumberOfRecords,2) > COMP_list = np.delete(COMP_list,i) > Not sure about the back

Re: [Numpy-discussion] record data previous to Numpy use

2017-07-07 Thread paul . carrico
Hi (all) Ounce again I would like to thanks the community for the supports. I progressing in moving my code to Python .. In my mind some parts remains quite hugly (and burns me the eyes), but it works and I'll optimized it in the future ; so far I can work with the data in a single reading

Re: [Numpy-discussion] record data previous to Numpy use

2017-07-07 Thread Derek Homeier
On 7 Jul 2017, at 1:59 am, Chris Barker wrote: > > On Thu, Jul 6, 2017 at 10:55 AM, wrote: > It's is just a reflexion, but for huge files one solution might be to > split/write/build first the array in a dedicated file (2x o(n) iterations - > one to identify the blocks size - additional one t