[Numpy-discussion] Season of Docs technical writer
I've updated my page (https://bennathanson.com/numpy2020) to include a section on Curation and Adaptation. ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Season of Docs technical writer
Hi Ben, On Fri, May 1, 2020, at 05:52, Ben Nathanson wrote: > I've updated my page (https://bennathanson.com/numpy2020) to include a > section on Curation and Adaptation. I enjoyed reading your page, and appreciate the wit sprinkled through your writing. I look forward to working with you this season! Best regards, Stéfan ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
[Numpy-discussion] Closing resolved good-first-issues
Hi all, I observed that there are many good-first-issues that are resolved but yet open. It would be a great help for new contributors if we could close them and label new good-first-issues (if not labelled already). Thanks and Regards Tina ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
Re: [Numpy-discussion] Closing resolved good-first-issues
On Fri, May 1, 2020 at 5:53 PM Tina Oberoi wrote: > Hi all, > > I observed that there are many good-first-issues that are resolved but yet > open. It would be a great help for new contributors if we could close them > and label new good-first-issues (if not labelled already). > Hi Tina, thanks for pointing that out. I have added you to the triage team, so you are able to close issues that you already noticed are fixed. I'll have a look at labelling some new ones now. Cheers, Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
[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 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').
Anirudh
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
