@ngoldbaum wheels building and tests are running fine for 3.13 and 3.14, you can have a look (just some small workflow changes)
Tests for matmul uses multithreading so for now it seems to work, maybe will add more extensive tests later

I edited the PR description since we would still need to fix the release automation to close numpy/numpy-quaddtype#30.

Tests for matmul uses multithreading so for now it seems to work

Is this an allusion to free-threaded support? You would need to add 3.13t and 3.14t builds to get free-threaded support. You've only added GIL-enabled 3.13 and 3.14 builds here.

I think you'd also need to declare free-threaded support in the extension too, otherwise the GIL will get enabled at runtime. See https://py-free-threading.github.io/porting-extensions/#declaring-free-threaded-support.

Probably worth adding pytest-run-parallel testing on the free-threaded build to the CI if you want to add free-threaded support.

I see, this make sense. Thanks for the pointers @ngoldbaum, will update the PR here after incorporating and testing this all on personal fork

************************** pytest-run-parallel report **************************
  All tests were run in parallel! 🎉
  ============================ no tests ran in 0.34s =============================
  ! _pytest.outcomes.Exit: GIL was dynamically re-enabled during test collection to load module 'numpy_quaddtype._quaddtype_main'. When running under a free-threaded interpreter with the GIL initially disabled, the test suite must not cause the GIL to be re-enabled at runtime. Check for compiled extension modules that do not use the 'Py_mod_gil' slot or the 'PyUnstable_Module_SetGIL' API. !

It seems the extension needs to be edited here, let's add this too in the tracker to keep the updates

It seems to be working as expected, @ngoldbaum please take a look

• Added pytest-run-parallel for 3.13t and 3.14t
• Updated the extension

We may need to expand the testing to cover thread-safety better

Thanks, now we just need to fix the release automation to make sure the sdist gets uploaded and then do a release!

Thanks, now we just need to fix the release automation to make sure the sdist gets uploaded and then do a release!

You mean within CI uploading sdist along with artifacts for every release?

yup! The wheels and sdist should be uploaded together once they're all built. I can point you at some examples in other repos if you need one.