Re: [Numpy-discussion] Call for Reviewers

Apologies for the wrong message about triage rights earlier and thanks for the clarification Matti! On Fri, May 22, 2020 at 5:13 AM Matti Picus wrote: > On 20/5/20 11:27 pm, Anirudh Subramanian wrote: > > Hi all, > > > > This topic was brought up in the triage meeting t

Re: [Numpy-discussion] Call for Reviewers

tag stale PR's. Just let me know where should I > start, or what would be most helpful. > > Thanks, > Mark > > On Wed, May 20, 2020, 1:29 PM Anirudh Subramanian > wrote: > >> Hi all, >> >> This topic was brought up in the triage meeting today. Numpy is

[Numpy-discussion] Call for Reviewers

Hi all, This topic was brought up in the triage meeting today. Numpy is seeing a huge surge in the number of PRs (current open PRs: 253) which could means two things: 1. Increase in volume of incoming PRs 2. Not enough reviewers to review the PRs. One thing that was discussed in the meeting was t

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

gt;> >> >> On Fri, May 8, 2020 at 11:56 AM Anirudh Subramanian < >> anirudh2...@gmail.com> wrote: >> >>> Hi all, >>> >>> There has been a discussion about divmod (1.0, 0.0) bug here : >>> https://github.com/numpy/numpy/issues/14900 an

[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

[Numpy-discussion] Deprecate inexact matches for mode, order etc ?

Hi all, I added a proposal to deprecate inexact and case insensitive matches for mode, order, searchside and sortkind. in https://github.com/numpy/numpy/pull/16056 , and this stemmed from a discussion started in https://github.com/numpy/numpy/pull/16007#discussion_r410517462 Currently, numpy allo