Incorrect module name in a stable ABI wheel?

[stumpylog]

I'm transitioning a project to use nanobind, and am seeing an oddity when building via cibuildwheel. I get a wheel like: "exifmwg-0.2.0-cp312-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64", but the compiled .so seems to be specific to Python 3.12: bindings.cpython-312-x86_64-linux-gnu.so

I've configured the stable ABI as such:

  nanobind_add_module(
    bindings
    NB_STATIC
    NB_SUPPRESS_WARNINGS
    STABLE_ABI
    LTO
    src/exifmwg/bindings.cpp
    ${CORE_SOURCES})

as well as

[tool.scikit-build]
build-dir = "build/{wheel_tag}"
wheel.py-api = "cp312"
wheel.packages = [ "src/exifmwg" ]

Maybe related to #1047

[wjakob]

Can you reproduce this outside of cibuildwheel?

[stumpylog]

Yes. Building with just uv build --wheel, after clearing dist and build folders, I get bindings.cpython-312-x86_64-linux-gnu.so inside a wheel named exifmwg-0.3.0-cp312-abi3-linux_x86_64.whl

nanobind == 2.7.0
scikit-build-core==0.11.4

[stumpylog]

The branch/repo, in case that helps: https://github.com/stumpylog/exifmwg/blob/feature/single-class/CMakeLists.txt

It has for the moment removed the sable ABI configuration