Re: [Numpy-discussion] Deprecate inexact matches for mode, order etc ?
On Fri, 2020-05-01 at 13:58 -0700, Anirudh Subramanian wrote:
> 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 allows :
> np.ravel_multi_index(arr, (7, 6), mode='Clip')
> np.ravel_multi_index(arr, (7, 6), mode='C')
> np.ravel_multi_index(arr, (7, 6), mode='cat')
>
> We have a similar story for order, searchside and sortkind. After the
> change, all non exact and case insensitive matches will give a
> deprecationwarning i.e. only exact matches for mode('clip', 'wrap'
> and
> 'raise'), order('C', 'F', 'A', 'K'), searchside ('left', 'right') and
> sortkind ('merge', 'heap', 'stable', 'quick') will be valid.
>
> The PR also includes 'byteorder' but i am not too sure about this
> since
> (as pointed out in the PR) sys.byteorder uses 'big', 'little' etc.
> while
> the numpy documentation uses single capital character to indicate
> byteorder
> ('S', 'L’, 'B', 'N', 'I').
Thanks for working on this.
For the byteorder, maybe we should just allow both for now? SciPy uses
"S" once, that is the default though. `=`, `>`, `<` (or "native", etc.)
are much nicer than `N`, `B`, `L` anyway, because that is what we
print. (I am not sure that `I`, which is also spelled `|`, has a useful
meaning as an argument to be honest.)
I think I would prefer allowing all of `>`, `B`, and `big`. But change
the documentation to not mention the single letter `B`. And some future
people/us can think about deprecating them in a few years...
In any case, I am absolutely +1 but would be very happy to e.g. keep
allowing single letter abbreviations if anyone thinks that they are
occasionally used out there.
Cheers,
Sebastian
>
> Anirudh
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@python.org
> https://mail.python.org/mailman/listinfo/numpy-discussion
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Update the Code of Conduct Committee Membership (new members wanted)
On Thu, Apr 23, 2020 at 11:38 PM Sebastian Berg wrote: > Hi all, > > it has come up in the last community call that many of our committee > membership lists have not been updated in a while. > This is not a big issue as such. But, while these committees are not > very active on a day-to-day basis, they are an important part of the > community and it is better to update them regularly and thus also > ensure they remain representative of the community. > Thanks Sebastian! > We would like to start by updating the members of the Code of Conduct > (CoC) committee. The CoC committee is in charge of responding and > following up to any reports of CoC breaches, as stated in: > > > https://docs.scipy.org/doc/numpy/dev/conduct/code_of_conduct.html#incident-reporting-resolution-code-of-conduct-enforcement > > If you are interested in or happy to serve on our CoC committee please > let me or e.g. Ralf Gommers know, join the next community meeting > (April 29th, 11:00PDT/18:00UTC), or reply on the list. > > I hope we will be able to discuss and reach a consensus between those > interested and involved quickly (possibly already on the next community > call). In either case, before any changes they will be run by the > mailing list to ensure community consensus. > Following up on this: Melissa and Anirudh both volunteered for this (thank you!), and in the last community call we discussed this (thumbs up from everyone there), and gave me the assignment to follow up on this list. Both Melissa and Anirudh have experience with CoC's, Melissa for the SciPy conference and Anirudh in the MXNet community. They're also two of the most active current contributors. So it will be great to have them on the committee. We also discussed that it would be good to have at least one current member remain, to have one steering council member who knows the project history well on the committee. Both Stefan and I have said that we're happy to stay on. So I would suggest that Stefan and I get together and figure out who of us that will be. And then we update the website and the CoC committee's private email list. Cheers, Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Update the Code of Conduct Committee Membership (new members wanted)
On 5/2/20, Ralf Gommers wrote: > On Thu, Apr 23, 2020 at 11:38 PM Sebastian Berg > > wrote: > >> Hi all, >> >> it has come up in the last community call that many of our committee >> membership lists have not been updated in a while. >> This is not a big issue as such. But, while these committees are not >> very active on a day-to-day basis, they are an important part of the >> community and it is better to update them regularly and thus also >> ensure they remain representative of the community. >> > > Thanks Sebastian! > > >> We would like to start by updating the members of the Code of Conduct >> (CoC) committee. The CoC committee is in charge of responding and >> following up to any reports of CoC breaches, as stated in: >> >> >> https://docs.scipy.org/doc/numpy/dev/conduct/code_of_conduct.html#incident-reporting-resolution-code-of-conduct-enforcement >> >> If you are interested in or happy to serve on our CoC committee please >> let me or e.g. Ralf Gommers know, join the next community meeting >> (April 29th, 11:00PDT/18:00UTC), or reply on the list. >> >> I hope we will be able to discuss and reach a consensus between those >> interested and involved quickly (possibly already on the next community >> call). In either case, before any changes they will be run by the >> mailing list to ensure community consensus. >> > > Following up on this: Melissa and Anirudh both volunteered for this (thank > you!), and in the last community call we discussed this (thumbs up from > everyone there), and gave me the assignment to follow up on this list. > > Both Melissa and Anirudh have experience with CoC's, Melissa for the SciPy > conference and Anirudh in the MXNet community. They're also two of the most > active current contributors. So it will be great to have them on the > committee. > > We also discussed that it would be good to have at least one current member > remain, to have one steering council member who knows the project history > well on the committee. Both Stefan and I have said that we're happy to stay > on. So I would suggest that Stefan and I get together and figure out who of > us that will be. And then we update the website and the CoC committee's > private email list. > Sounds good. Thanks Sebastian, Ralf, Anirudh and Melissa! Warren > Cheers, > Ralf > ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
