[Numpy-discussion] timedelta64 remainder behavior with div by 0
wieser.eric+numpy at gmail.com
Tue Jan 8 13:27:57 EST 2019
If we consider it a bug, we could patch it in 1.16.1 (or are we still
waiting on 1.16.0?), which would minimize the backwards compatibility cost.
On Tue, 8 Jan 2019 at 10:05 Stefan van der Walt <stefanv at berkeley.edu>
> On Tue, 08 Jan 2019 09:57:03 -0800, Tyler Reddy wrote:
> > np.timedelta64(5) % np.timedelta64(0) -> numpy.timedelta64(0)
> > In contrast, np.float64(1) % np.float64(0) -> nan
> > There's a suggestion that we should switch to returning NaT for the
> > timedelta64 case for consistency, and that this probably isn't too
> > given how recent these additions are.
> That seems like a reasonable change to me; one could probably consider the
> previous behavior a bug?
> NumPy-Discussion mailing list
> NumPy-Discussion at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NumPy-Discussion