Henry Schreiner

(Copied from https://github.com/pypa/wheel/discussions/654): These tests are trying to test build isolation, which won't ever just package up the Fedora packages and make wheels out of them, it will always pull...

The non-network tests (usually called PEP 517 tests in our suite) do test against the installed version by using no-build-isolation. It's the PEP 518 tests that need wheels to install,...

Maybe we should make a non-isolated build version of those tests then?

I'm going to be converting pybind11 over to scikit-build-core soon, though it will be a little more than a simple example due to the "global" package. Nanobind is not quite...

I recommend this guide, by the way, which includes cibuildwheel and lots of other information: https://learn.scientific-python.org/development/guides/gha-wheels

And if you use pyproject.toml config for cibuildwheel, you can run cibuildwheel locally / on other CIs, too. Also, the Python version you use to build the SDist and run...

I think this is hitting something well before that. I'm playing around with https://github.com/petrasvestartas/test_my_binding/pull/1

You should only publish on tags or releases, it's trying to publish all the time. I'd highly recommend using the GitHub action, and using Trusted Publisher for PyPI (or Test...

I'd try reducing the number of build threads. I bet it's building in parallel, and there's not enough memory on the Windows build bot to handle it. It's pretty common...

And yes, header-only libraries take a lot of memory to compile. Nanobind isn't fully header only, but I think it's heavily templated, and CGal is likely really bulky and header-only....