[Numpy-discussion] Depreciating asfortranarray and ascontiguousarray

Stephan Hoyer shoyer at gmail.com
Fri Oct 26 19:26:09 EDT 2018


On Fri, Oct 26, 2018 at 3:48 PM Sebastian Berg <sebastian at sipsolutions.net>
wrote:

> On Fri, 2018-10-26 at 13:25 -0700, Stephan Hoyer wrote:
> > On Fri, Oct 26, 2018 at 12:55 PM Alex Rogozhnikov <
> > alex.rogozhnikov at yandex.ru> wrote:
> > >
> > > The conservative way to handle this would be to do a deprecation
> > > cycle, specifically by issuing FutureWarning when scalars or 0d
> > > arrays are encountered as inputs.
> > > Sounds good to me. Behavior should be scheduled for numpy 1.18?
> > >
> >
> > Yes, that sounds about right to me.
> >
>
> Is there a way to avoid the future warning? An unavoidable warning in a
> widely used function seems really annoying to me. Unless, the 0d thing
> happens rarely, but then it might be the downstream users that get the
> warning for no reason.
>
> - Sebastian
>

My suspicion is that 0d arrays are rarely used as arguments to
ascontiguousarray / asfortranarray. But it's hard to say for sure...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20181026/b98e8f01/attachment.html>


More information about the NumPy-Discussion mailing list