On Thu, Jul 19, 2012 at 2:53 PM, Travis Oliphant wrote:
>
> On Jul 19, 2012, at 3:50 AM, Nathaniel Smith wrote:
>
>> So the underlying problem with the controversial inplace_increment
>> PR[1] is that currently, there's actually nothing in the public numpy
>> API that exposes the workings of numpy
On Jul 19, 2012, at 3:50 AM, Nathaniel Smith wrote:
> So the underlying problem with the controversial inplace_increment
> PR[1] is that currently, there's actually nothing in the public numpy
> API that exposes the workings of numpy indexing. The only thing you
> can do with a numpy index is cal
So the underlying problem with the controversial inplace_increment
PR[1] is that currently, there's actually nothing in the public numpy
API that exposes the workings of numpy indexing. The only thing you
can do with a numpy index is call ndarray.__getattr__ or __setattr__.
This is a pretty obvious