Mailman 3 January 2025 - NumPy-Discussion

next NumPy Optimization Team meeting - Monday, January 20th, 2025 at 5 pm UTC
by Inessa Pawson June 5, 2026

June 5, 2026

Hi, all! The next NumPy Optimization Team meeting will be held on Monday, January 20th at 17:00 UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/81261288210?pwd=iwV99tGSjR61RTGEERKM4QKxe46g… Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to discuss, follow the link: https://hackmd.io/dVdSlQ0TThWkOk0OkmGsmw?both For the notes from the previous meetings, visit: https://github.com/numpy/archive/tree/main/optim_team_meetings -- Cheers, Inessa Inessa Pawson GitHub: inessapawson

1 23

Fixing definition of reduceat for Numpy 2.0?
by Martin Ling Feb. 27, 2026

Feb. 27, 2026

Hi folks, I don't follow numpy development in much detail these days but I see that there is a 2.0 release planned soon. Would this be an opportunity to change the behaviour of 'reduceat'? This issue has been open in some form since 2006! https://github.com/numpy/numpy/issues/834 The current behaviour was originally inherited from Numeric, and makes reduceat often unusable in practice, even where it should be the perfect, concise, efficient solution. But it has been impossible to change it without breaking compatibіlity with existing code. As a result, horrible hacks are needed instead, e.g. my answer here: https://stackoverflow.com/questions/57694003 Is this something that could finally be fixed in 2.0? Martin

6 12

next NumPy Newcomers' Hour - June 27th, 2024 at 10 pm UTC
by Inessa Pawson Sept. 12, 2025

Sept. 12, 2025

Our next Newcomers' Hour will be held TOMORROW, June 27th at 10 pm UTC. Stop by to ask questions, share your progress, celebrate success, or just to say hi. To add to the meeting agenda the topics you’d like to discuss, follow the link: https://hackmd.io/3f3otyyuTte3FU9y3QzsLg?both. Join the meeting via Zoom: https://us06web.zoom.us/j/82563808729?pwd=ZFU3Z2dMcXBGb05YemRsaGE1OW5nQT09. -- Cheers, Inessa Inessa Pawson GitHub: inessapawson

1 11

next NumPy triage meeting - Wednesday, January 22nd, 2025 at 6 pm UTC
by Inessa Pawson May 11, 2025

May 11, 2025

The next NumPy triage meeting will be held this Wednesday, January 22nd at 18:00 UTC. As always, this is a meeting where we synchronously triage prioritized PRs and issues. Everyone is welcome to attend and contribute to a conversation. Join us via Zoom: https://numfocus-org.zoom.us/j/82096749952?pwd=MW9oUmtKQ1c3a2gydGk1RTdYUUVX… Please notify us of issues or PRs that you’d like to have reviewed by adding a GitHub link to them in the meeting agenda: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg -- Cheers, Inessa Inessa Pawson GitHub: inessapawson

1 7

next Documentation team meeting
by Mukulika Pahari May 5, 2025

May 5, 2025

Hi all, Our next Documentation Team meeting will happen on *Monday, July 15* at *7PM UTC*. All are welcome - you don't need to already be a contributor to join. If you have questions or are curious about what we're doing, we'll be happy to meet you! If you wish to join on Zoom, use this (updated) link: https://numfocus-org.zoom.us/j/85016474448?pwd=TWEvaWJ1SklyVEpwNXUrcHV1YmFJQ... Here's the permanent hackmd document with the meeting notes (still being updated): https://hackmd.io/oB_boakvRqKR-_2jRV-Qjg Hope to see you around! Best wishes, Mukulika

2 18

next NumPy community meeting - June 5th, 2024 at 6 pm UTC
by Inessa Pawson March 22, 2025

March 22, 2025

The next NumPy community meeting will be held this Wednesday, June 5th at 6 pm UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/83278611437?pwd=ekhoLzlHRjdWc0NOY2FQM0NPemdk… . Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to discuss, follow the link: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both. For the notes from the previous meetings, visit: https://github.com/numpy/archive/tree/main/community_meetings. -- Cheers, Inessa Inessa Pawson GitHub: inessapawson

1 19

slice an array along specific axis
by Michael Mullen Feb. 1, 2025

Feb. 1, 2025

Hello, I am writing a class handling NumPy arrays, and basing it off some computations I have done in C++ using the Eigen library. For tensors whose length are only known at runtime, the Eigen chip method is useful for slicing a tensor along a specific axis while keeping all other axes the same. I have not found a similar method in NumPy, but a simple implementation is def chip(A, axis, vals): return np.swapaxes(np.swapaxes(A, axis, -1)[..., vals], -1, axis) Example usage would be (to slice the 3rd axis of a 4D array): A = np.random.randn(10,11,12,13) B = chip(A, axis=2, vals=np.arange(0,6)) B.shape #(10, 11, 6, 13) Since this may be useful for others, despite its simplicity, I thought it may be useful to have something similar in NumPy. Best, Mike

2 1

Scientific Python Translations sprint - join us!
by Melissa Mendonça Jan. 30, 2025

Jan. 30, 2025

Hi all! As part of the Scientific Python Translations project [1], we are organizing a full-day sprint to answer questions and meet new volunteer contributors interested in working on Scientific Python project website translations. Currently, we are accepting translations for NumPy, SciPy, NetworkX, Zarr, pandas and Xarray, but more project may join in the future. The sprint will take place on **February 11th from 11AM UTC to 9PM UTC on the Scientific Python Discord server** [2]. You are free to join or leave at any time during those hours, and you can stay for any amount of time. You can choose to work on your own, or you can team up with other translators and discuss specific issues.This is a great opportunity for first-time contributors as the only requirement is a working knowledge of English and proficiency in the target translation language - although familiarity with the project being translated is useful. We encourage you to participate even if you are not sure you fulfill these requirements. Target languages include Spanish, Chinese (Simplified), Japanese, Portuguese (Brazilian), Arabic and Hindi. You can find more information on the translation process in our documentation [3] or join the #translation channel of the Scientific Python Discord server. You can also find this announcement in the Scientific Python discourse, if you want to have a link to share with your network: https://discuss.scientific-python.org/t/scientific-python-translations-spri… [1] https://blog.scientific-python.org/scientific-python/translations/ [2] https://discord.com/invite/vur45CbwMz (Scientific Python Discord server invite) [3] https://scientific-python-translations.github.io/ Cheers! - Melissa

1 0

NumPy 2.2. 2 Release
by Charles R Harris Jan. 19, 2025

Jan. 19, 2025

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.2.2. NumPy 2.2.2 is a patch release that fixes bugs found after the 2.2.1 release. The number of typing fixes/updates is notable. This release supports Python 3.10-3.13. Wheels can be downloaded from PyPI <https://pypi.org/project/numpy/2.2.2>; source archives, release notes, and wheel hashes are available on Github <https://github.com/numpy/numpy/releases/tag/v2.2.2>. *Contributors* A total of 8 people contributed to this release. People with a "+" by their names contributed a patch for the first time. - Alicia Boya García + - Charles Harris - Joren Hammudoglu - Kai Germaschewski + - Nathan Goldbaum - PTUsumit + - Rohit Goswami - Sebastian Berg *Pull requests merged* A total of 16 pull requests were merged for this release. - #28050: MAINT: Prepare 2.2.x for further development - #28055: TYP: fix ``void`` arrays not accepting ``str`` keys in ``__setitem__`` - #28066: TYP: fix unnecessarily broad ``integer`` binop return types (#28065) - #28112: TYP: Better ``ndarray`` binop return types for ``float64`` &... - #28113: TYP: Return the correct ``bool`` from ``issubdtype`` - #28114: TYP: Always accept ``date[time]`` in the ``datetime64`` constructor - #28120: BUG: Fix auxdata initialization in ufunc slow path - #28131: BUG: move reduction initialization to ufunc initialization - #28132: TYP: Fix ``interp`` to accept and return scalars - #28137: BUG: call PyType_Ready in f2py to avoid data races - #28145: BUG: remove unnecessary call to PyArray_UpdateFlags - #28160: BUG: Avoid data race in PyArray_CheckFromAny_int - #28175: BUG: Fix f2py directives and --lower casing - #28176: TYP: Fix overlapping overloads issue in 2->1 ufuncs - #28177: TYP: preserve shape-type in ndarray.astype() - #28178: TYP: Fix missing and spurious top-level exports Cheers, Charles Harris

1 0

New GitHub issue UI
by Nathan Jan. 15, 2025

Jan. 15, 2025

Hi all, GitHub is rolling out the new UI for issues, which includes a lot of new opportunities to reorganize our backlog. More detail on the changelog blog: https://github.blog/changelog/2025-01-13-evolving-github-issues-public-prev… In particular, there is now much richer support for tracking issues by marking issues as "sub-issues". We can also (finally) get rid of the issue category labels - GitHub now has support for "issue types". If someone with triage rights would like to take this on, it would be a nice project to try to go through the backlog and update things to use the new system, as well as the bot that auto-applies labels. You could probably use a script rather than doing it manually. -Nathan

3 2