I guess that one's a judgement call. I lean towards it being okay to just
make those be an error, but others might disagree...

On Wed, Mar 6, 2013 at 10:20 PM, seberg <notifications@github.com> wrote:

> In doc/release/1.8.0-notes.rst:
>
> > @@ -54,6 +54,13 @@ The function np.take now allows 0-d arrays as indices.
> >
> >  The separate compilation mode is now enabled by default.
> >
> > +The functions np.insert and np.delete now handle out of bound indices like
> > +normal indexing instead of ignoring them, this strongly affects negative ones.
> > +FutureWarnings will be raised for boolean indices which will change behaviour.
> > +Insert allows multiple insertions at single scalar since numpy 1.7. and now
> > +further allows this for a one item sequence. There are subtle differences
> > +because the scalar expects N arrays, while the sequence expects size N along
> > +the axis.
>
> Yes, I will change it to a future warning for negative indices. What about
> out of bound indices, an error is OK in that case right?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/numpy/numpy/pull/452/files#r3270944>
> .
>