Hi all,
I would like to try to reach a consensus about a long standing inconsistent
behavior of reduceat() reported and discussed here
https://github.com/numpy/numpy/issues/834
In summary, it seems an elegant and logical design choice, that all users
will expect, for
out = ufunc.reduc
Discussion on-going at the above issue, but perhaps worth mentioning
more broadly the alternative of adding a slice argument (or start,
stop, step arguments) to ufunc.reduce, which would mean we can just
deprecate reduceat altogether, as most use of it would just be
add.reduce(array, slice=slice(i
