[Numpy-discussion] Question regarding transitioning native extension to NumPy 2.0

I am working to transition mkl_fft and mkl_random to NumPy 2.0. Both of these projects contain native extensions. I have distilled unexpected behavior behind observed test failures in minimal C extension: https://github.com/oleksandr-pavlyk/reproducer-for-question-about-numpy2 The extension def

Re: [Numpy-discussion] Set #threads from within python code

Rather than keeping the number of threads MKL uses to 1, it is better to use MKL_THREADING_LAYER=SEQUENTIAL https://software.intel.com/en-us/node/528380 --Sasha From: NumPy-Discussion [mailto:numpy-discussion-bounces+oleksandr.pavlyk=intel@python.org] On Behalf Of Neal Becker Sent: Friday

[Numpy-discussion] How to get sources of the current state of 1.16?

Are they the same as the current master, or is there a mechanism to query issue tracker for all PRs designated to make it into 1.16? Even then, what should the base be? Perhaps this is already documented in either an issue or a PR. Thanks for the pointer. Sasha

Re: [Numpy-discussion] How to get sources of the current state of 1.16?

GitHub Milestone for 1.16: https://github.com/numpy/numpy/milestone/58 On Thu, Nov 29, 2018 at 11:54 AM Pavlyk, Oleksandr mailto:oleksandr.pav...@intel.com>> wrote: Are they the same as the current master, or is there a mechanism to query issue tracker for all PRs designated to make it int