Mailman 3 July 2025 - NumPy-Discussion

next NumPy community meeting - Wednesday, April 9th, 2025 at 5 pm UTC - now meeting ONE HOUR EARLIER
by Inessa Pawson March 7, 2026

March 7, 2026

The next NumPy community meeting will be held this Wednesday, April 9th at 17:00 (5 pm) UTC. Please note the TIME CHANGE! 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 24

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 Optimization Team meeting - Monday, January 20th, 2025 at 5 pm UTC
by Inessa Pawson Feb. 20, 2026

Feb. 20, 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 18

next NumPy triage meeting - Wednesday, May 28th, 2025 at 5 pm UTC
by Inessa Pawson Jan. 4, 2026

Jan. 4, 2026

The next NumPy triage meeting will be held this Wednesday, May 28th at 17:00 (5 pm) UTC. 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 14

ENH: Add a non-circular shift function
by Carlos Martin Nov. 23, 2025

Nov. 23, 2025

Feature request: Add a non-circular shift function that is similar to [`numpy.roll`](https://numpy.org/doc/stable/reference/generated/numpy.roll.html) but, instead of wrapping elements around, replaces unoccupied entries with a specified fill value. Examples: ``` >>> import numpy as np >>> a = np.arange(1, 6) >>> a array([1, 2, 3, 4, 5]) >>> np.shifted(a, 2) array([0, 0, 1, 2, 3]) >>> np.shifted(a, -2) array([3, 4, 5, 0, 0]) >>> a = np.arange(1, 10).reshape((3, 3)) >>> a array([[1, 2, 3], [4, 5, 6], [7, 8, 9]]) >>> np.shifted(a, (1, -2), (0, 1)) array([[0, 0, 0], [3, 0, 0], [6, 0, 0]]) ``` Prior discussion: https://github.com/numpy/numpy/issues/26220 Pull request: https://github.com/numpy/numpy/pull/29389

1 1

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

NumPy security roadmap proposal
by Ralf Gommers July 29, 2025

July 29, 2025

Hi all, In https://github.com/numpy/numpy/issues/29178 I posted a proposal for steps to take to improve supply chain security. The most important proposed change is: - Move building release artifacts that get uploaded to PyPI and anaconda.org to a new repository. Other proposed changes: - Further tighten 2FA requirements for everyone with any permissions beyond read-only on the repository. - Move GITHUB_TOKEN to read-only default permissions. - Start shipping SBOMs, in the way outlined by PEP 770 - Start verifying that our builds are fully reproducible It looks like everyone is happy with the proposal so far. Posting here for visibility. Please comment if you have any concerns or other feedback. We'll start implementation next week if there are no blocking concerns. For 2FA and repository/PyPI access, we'll start making changes soon. Note that GitHub has recently made changes to its 2FA settings that ask for action from many people: on https://github.com/orgs/numpy/people you can see that under "Two-factor authentication" the options increased; there is now a Secure/Insecure distinction instead of only Enabled/Disabled. If you want to move yourself from Insecure to Secure, you have to disable the SMS/mobile recovery option in your personal settings under "Password and authentication". A large majority of the 94 people with permissions are currently marked as Insecure. Cheers, Ralf

3 4

a use case for __array_interface__ "scalar" path?
by marco.rigobello＠hotmail.com July 26, 2025

July 26, 2025

Hi, I was trying to prevent array creation from iterating over instances of classes implementing __iter__, __getitem__, __len__ etc. An effective way (at least with a UserDict subclass) seem setting __array_interface__ = {"shape": (), "typestr": "O"} # with data field omitted (!) According to the docs https://numpy.org/devdocs/reference/arrays.interface.html#object.__array_in… "Not specifying this field uses a “scalar” path that we may remove in the future as we are not aware of any users." I am new to __array_interface__, so this might be a bad approach (*). If not, this seems to be a good reason for *not* removing. Note there is demand for avoiding coercion of custom types into new dimensions: https://stackoverflow.com/q/43722023 https://stackoverflow.com/q/70460738 https://stackoverflow.com/q/22290204 https://github.com/numpy/numpy/issues/27212 https://github.com/numpy/numpy/issues/27382 (*) Still, other attempts partially messed up with class functionality (e.g., __len__ = None) or did not work at all: __iter__ = None (TypeError: Could not convert object to sequence) implementing __array__ (RecursionError: maximum recursion depth exceeded) Cheers, Marco

1 0

NumPy 2.3.2 released
by Charles R Harris July 24, 2025

July 24, 2025

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.3.2. The NumPy 2.3.2 release is a patch release with a number of bug fixes and maintenance updates. The highlights are: - Wheels for Python 3.14.0rc1 - PyPy updated to the latest stable release - OpenBLAS updated to 0.3.30 This release supports Python 3.11-3.14. Wheels can be downloaded from PyPI <https://pypi.org/project/numpy/2.3.2>; source archives, release notes, and wheel hashes are available on Github <https://github.com/numpy/numpy/releases/tag/v2.3.2>. *Contributors* A total of 9 people contributed to this release. People with a "+" by their names contributed a patch for the first time. - !DWesl - Charles Harris - Joren Hammudoglu - Maanas Arora - Marco Edward Gorelli - Matti Picus - Nathan Goldbaum - Sebastian Berg - kostayScr + *Pull requests merged* A total of 16 pull requests were merged for this release. - #29256: MAINT: Prepare 2.3.x for further development - #29283: TYP: Work around a mypy issue with bool arrays (#29248) - #29284: BUG: fix fencepost error in StringDType internals - #29287: BUG: handle case in mapiter where descriptors might get replaced... - #29350: BUG: Fix shape error path in array-interface - #29412: BUG: Allow reading non-npy files in npz and add test - #29413: TST: Avoid uninitialized values in test (#29341) - #29414: BUG: Fix reference leakage for output arrays in reduction functions - #29415: BUG: fix casting issue in center, ljust, rjust, and zfill (#29369) - #29416: TYP: Fix overloads in ``np.char.array`` and ``np.char.asarray``... - #29417: BUG: Any dtype should call ``square`` on ``arr \*\* 2`` (#29392) - #29424: MAINT: use a stable pypy release in CI - #29425: MAINT: Support python 314rc1 - #29429: MAINT: Update highway to match main. - #29430: BLD: use github to build macos-arm64 wheels with OpenBLAS and... - #29437: BUG: fix datetime/timedelta hash memory leak (#29411) Cheers, Charles Harris

1 0

Python 3.14rc1 is out.
by Charles R Harris July 22, 2025

July 22, 2025

Hi All, Just a note. Chuck

2 4