Proper 3.13 build on github actions (not cp312-abi3)

[alecjacobson]

Apologies if this turns out to have nothing to do with nanobind. I'm struggling to get my wheel build on github actions to produce a proper cp313 wheel. log and wheels.yml.

Does anyone know how to achieve this? Is there a flag I'm missing somewhere? Is nanobind actually involved in that?

[alecjacobson]

It seems like drjit is managing to do it https://pypi.org/project/drjit/#files

[alecjacobson]

Ah, so I had

# Build stable ABI wheels for CPython 3.12+
wheel.py-api = "cp312"

in my pyproject.yml

I changed that to cp313 and we'll see if it works / doesn't break the other builds. I guess I don't understand whether this needs to be here or even what abi truly is (my guess is that it's trying to be forward compatible?).

[alecjacobson]

Ok, I think it was related to nanobind in the end. Leaving wheel.py-api = "cp312" in place and only compiling up to cp312 (not cp313) seems find so long as I add the STABLE_ABI flag to my nanobind_add_module calls. This seems to match the nanobind documentation https://nanobind.readthedocs.io/en/latest/faq.html#can-i-make-stable-abi-extensions-for-pre-3-12-python https://nanobind.readthedocs.io/en/latest/api_cmake.html#command:nanobind_add_module
So no issue on the nanobind end, just me getting up to speed and knowing what to look for in the nanobind doc.

[wjakob]

There are some issues with stable ABI builds when using Python 3.13 atm, I will look into them after the SIGGRAPH Asia deadline..