Trouble using pyproject.toml for limited api

[krpatter-intc]

Trouble using pyproject.toml for limited api

[krpatter-intc]

I misunderstood that the line was creating and new file for setup.cfg during the build. Yes, creating and making a new setup.cfg fixed it, or for folks doing just a pyproject.toml, the trick is to add:

[tool.distutils.bdist_wheel]
py_limited_api = "cp38"

[davidhewitt]

Closing as we've documented a few solutions now between these issues, PRs and the README. Thanks again!

[davidhewitt]

Thanks for the report, I'll try to take a look in the coming days.

it doesn't build with the limited api

Can I check what you're doing to determine to verify that?

[krpatter-intc]

The resulting .whl with python setup.py bdist_wheel --py-limited-api=cp38 is:

mytarget-0.0.1-cp38-abi3-win_amd64.whl

But with python -m build it is still:

mytarget-0.0.1-cp39-cp39-win_amd64.whl

[davidhewitt]

Ah I see. Probably what is happening is that the Rust build is using the limited API but the bdist_wheel command isn't, so that's why the wheel name is wrong.

You could try creating a file, point the DIST_EXTRA_CONFIG environment variable at it, and set bdist_wheel to use the limited API in that file.

For example we do this in CI at

setuptools-rust/.github/workflows/ci.yml

Line 164 in 58266f2

echo -e "[bdist_wheel]\npy_limited_api=cp39" > $DIST_EXTRA_CONFIG

Probably we need to update some documentation

[krpatter-intc]

I tried a few variations on that: (i'm on windows)

set DIST_EXTRA_CONFIG=[bdist_wheel]\npy_limited_api=cp39
python -m build -w --config-setting=--py-limited-api=cp38 --no-isolation

but so far no luck

also tried directly putting the setting in to the toml:

[bdist_wheel]
py-limited-api = "cp39"
py_limited_api = "cp39"

[krpatter-intc]

I looked through that example and the test, and the main difference between what I have and that test is that I have 100% pyproject.toml (well...i have setuptools.setup() but that's it)

[krpatter-intc]

Submitted #400 to document