Deprecation warnings are just to give people a heads up, and only visible
if explicitly requested. The functionality *is* deprecated; we might as
well start giving people that heads up in the standard way now, and they
can figure out for themselves when they want to make the change.
On 2 Mar 2013 14:44, "seberg" <notifications@github.com> wrote:

> In numpy/core/src/multiarray/nditer_constr.c:
>
> > @@ -158,6 +156,16 @@
> >          return NULL;
> >      }
> >
> > +    /*
> > +     * Before 1.8, if `oa_ndim == 0`, this meant `op_axes != NULL` was an error.
> > +     * With 1.8, `oa_ndim == -1` takes this role, while op_axes in that case
> > +     * enforces a 0-d iterator. At some point this should be deprecated, but
> > +     * third party software must use `oa_ndim == 0` for <1.8 compatibility.
> > +     */
> > +    if ((oa_ndim == 0) && (op_axes == NULL)) {
> > +        oa_ndim = -1;
>
> @njsmith <https://github.com/njsmith>, because DEPRECATE spits out
> warnings. And you cannot change to -1 if you want to support <1.8 (it is
> not well defined for those versions). So effectively I think that third
> party code cannot really use -1 yet and thus deprecating it before we can
> say that 1.8. is old seemes not right...
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/numpy/numpy/pull/3104/files#r3215077>
> .
>