Hi All, We plan to release NumPy 1.26 soon after the release of the Python 3.12.0rc1 release, which is currently scheduled for July 31, just a bit more than two weeks off. What I'd like to do is
1. Tag the commit after v1.25.1 -- f9e85438782cc5 -- as 'v1.26.0.dev0', marking it as the start of 1.26 development. 2. Backport the `meson.build` files from main. This is mostly automatic, but a few changes need to be made. 3. Backport the files for spin builds. 4. Begin testing the Python 3.12 betas 5. Update OpenBLAS when we are happy with it. 6. Wait for SIMD support? I'm wondering if we can split the builds, using distutils for Python 3.9-3.11 and meson only for 3.12, or if that is even worth the trouble. Thoughts? Chuck
_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: arch...@mail-archive.com
