Re: [Numpy-discussion] divmod(1.0, 0.0) bug

Thanks for your inputs, Brock and Stephan. > (However, note that the backwards compatibility policy you link to is only a draft, not officially accepted.) Yes, I didn't realize that. Thanks for pointing that out. In practice from the little I have seen, I find the NEP very close to what is being

Re: [Numpy-discussion] divmod(1.0, 0.0) bug

On Fri, May 8, 2020 at 4:10 PM Brock Mendel wrote: > FWIW in pandas we post-process floordiv (and divmod) ops to get the > "Expected Result" behavior from the OP. > > > On Fri, May 8, 2020 at 11:56 AM Anirudh Subramanian > wrote: > >> Hi all, >> >> There has been a discussion about divmod (1.0,

Re: [Numpy-discussion] divmod(1.0, 0.0) bug

FWIW in pandas we post-process floordiv (and divmod) ops to get the "Expected Result" behavior from the OP. On Fri, May 8, 2020 at 11:56 AM Anirudh Subramanian wrote: > Hi all, > > There has been a discussion about divmod (1.0, 0.0) bug here : > https://github.com/numpy/numpy/issues/14900 and >

[Numpy-discussion] divmod(1.0, 0.0) bug

Hi all, There has been a discussion about divmod (1.0, 0.0) bug here : https://github.com/numpy/numpy/issues/14900 and https://github.com/numpy/numpy/pull/16161 . *SUMMARY* Currently divmod(1.0, 0.0) sets the "Invalid error" and returns (nan, nan). This is not consistent with IEEE 754