Re: [Numpy-discussion] some typestrings not recognized anymore

2012-06-03 Thread Benjamin Root
On Sunday, June 3, 2012, Ralf Gommers wrote: > > > On Sun, Jun 3, 2012 at 4:49 PM, Nathaniel Smith > > > wrote: > >> On Sun, Jun 3, 2012 at 3:28 PM, Ralf Gommers >> > 'ralf.gomm...@googlemail.com');>> wrote: >> > Hi, >> > >> > Just ran into this: >> > >> np.__version__ >> > '1.5.1' >>

Re: [Numpy-discussion] fast access and normalizing of ndarray slices

2012-06-03 Thread srean
Hi Wolfgang, I think you are looking for reduceat( ), in particular add.reduceat() -- srean On Thu, May 31, 2012 at 12:36 AM, Wolfgang Kerzendorf wrote: > Dear all, > > I have an ndarray which consists of many arrays stacked behind each other > (only conceptually, in truth it's a normal 1d f

Re: [Numpy-discussion] some typestrings not recognized anymore

2012-06-03 Thread Ralf Gommers
On Sun, Jun 3, 2012 at 4:49 PM, Nathaniel Smith wrote: > On Sun, Jun 3, 2012 at 3:28 PM, Ralf Gommers > wrote: > > Hi, > > > > Just ran into this: > > > np.__version__ > > '1.5.1' > np.empty((1,), dtype='>h2') # works in 1.6.2 too > > array([0], dtype=int16) > > > np.__version__

[Numpy-discussion] Issue tracking

2012-06-03 Thread Charles R Harris
Hi All, The issue tracking discussion seems to have died. Since github issues looks to be a viable alternative at this point, I propose to turn it on for the numpy repository and start directing people in that direction. Thoughts? Chuck ___ NumPy-Discu

Re: [Numpy-discussion] better error message possible?

2012-06-03 Thread Charles R Harris
On Fri, Jun 1, 2012 at 10:56 AM, Chris Withers wrote: > On 01/06/2012 16:39, Benjamin Root wrote: > > > > > > > >>> import numpy > > > >>> numpy.zeros(10)[-123] > > > Traceback (most recent call last): > > > File "", line 1, in > > > IndexError: index out of bounds > >

[Numpy-discussion] NumPy release manager post

2012-06-03 Thread Ralf Gommers
Hi all, You probably remember that I said that after numpy 1.7.0 was out I wanted to step down as release manager for NumPy and focus more on SciPy. That was 4.5 months ago, and now that 1.7.0 keeps being postponed I'm actually planning to not wait for it. I have found that it's not possible for m

Re: [Numpy-discussion] commit rights for Nathaniel

2012-06-03 Thread Ralf Gommers
On Sun, Jun 3, 2012 at 6:43 PM, Charles R Harris wrote: > Hi All, > > Numpy is approaching a time of transition. Ralf will be concentrating his > efforts on Scipy I'll write a separate post on that asap. > and I will be cutting back on my work on Numpy. I sincerely hope you don't cut back on

[Numpy-discussion] commit rights for Nathaniel

2012-06-03 Thread Charles R Harris
Hi All, Numpy is approaching a time of transition. Ralf will be concentrating his efforts on Scipy and I will be cutting back on my work on Numpy. The 1.7 release looks to be delayed and I suspect that the Continuum Analytics folks will become increasingly dedicated to the big data push. We need

Re: [Numpy-discussion] some typestrings not recognized anymore

2012-06-03 Thread Nathaniel Smith
On Sun, Jun 3, 2012 at 3:28 PM, Ralf Gommers wrote: > Hi, > > Just ran into this: > np.__version__ > '1.5.1' np.empty((1,), dtype='>h2')  # works in 1.6.2 too > array([0], dtype=int16) > np.__version__ > '1.7.0.dev-fd78546' np.empty((1,), dtype='>h2') > Traceback (most recent c

[Numpy-discussion] some typestrings not recognized anymore

2012-06-03 Thread Ralf Gommers
Hi, Just ran into this: >>> np.__version__ '1.5.1' >>> np.empty((1,), dtype='>h2') # works in 1.6.2 too array([0], dtype=int16) >>> np.__version__ '1.7.0.dev-fd78546' >>> np.empty((1,), dtype='>h2') Traceback (most recent call last): File "", line 1, in TypeError: data type ">h2" not underst