Re: [Numpy-discussion] Questionable reduceat behavior

2011-08-16 Thread Wes McKinney
On Sun, Aug 14, 2011 at 11:58 AM, Wes McKinney wrote: > On Sat, Aug 13, 2011 at 8:06 PM, Mark Wiebe wrote: >> Looks like this is the second-oldest open bug in the bug tracker. >> http://projects.scipy.org/numpy/ticket/236 >> For what it's worth, I'm in favour of changing this behavior to be more

Re: [Numpy-discussion] Questionable reduceat behavior

2011-08-14 Thread Wes McKinney
On Sat, Aug 13, 2011 at 8:06 PM, Mark Wiebe wrote: > Looks like this is the second-oldest open bug in the bug tracker. > http://projects.scipy.org/numpy/ticket/236 > For what it's worth, I'm in favour of changing this behavior to be more > consistent as proposed in that ticket. > -Mark > > On Thu,

Re: [Numpy-discussion] Questionable reduceat behavior

2011-08-13 Thread Mark Wiebe
Looks like this is the second-oldest open bug in the bug tracker. http://projects.scipy.org/numpy/ticket/236 For what it's worth, I'm in favour of changing this behavior to be more consistent as proposed in that ticket. -Mark On Thu, Aug 11, 2011 at 11:25 AM, Wes McKinney wrote: > I'm a littl

[Numpy-discussion] Questionable reduceat behavior

2011-08-11 Thread Wes McKinney
I'm a little perplexed why reduceat was made to behave like this: In [26]: arr = np.ones((10, 4), dtype=bool) In [27]: arr Out[27]: array([[ True, True, True, True], [ True, True, True, True], [ True, True, True, True], [ True, True, True, True], [ True, T