Joe Rickerby

You can test a project using something like this in a github workflow- ```yaml - name: Build wheels uses: ririv/cibuildwheel@main ```

Looks good to me! @mhsmith what do you think?

Ah, I hadn't considered that we could run the whole build under rosetta emulation! It's quite a nice idea, given how awkward cross-builds can be, and how fast Rosetta 2...

> Apple has also said macOS 27 is the last to fully support Rosseta 2 Interesting. > We need to improve cross-compiles eventually, maybe it makes sense to introduce a...

Thank you for these pointers @rgommers! My PEP knowledge was way out-of-date, I was thinking of the [draft PEP](https://github.com/benfogle/cross-compile-pep-draft/blob/2e8bb183af6de4622f2657973ab42bccbbaa49d4/pep-9999.rst) by @benfogle, which does include a build-backend switch. So, PEP 739...

Also, I did have a thought, if you want to choose to use Rosetta 2 for the compilation, you could invoke cibuildwheel itself with `arch -x86_64 cibuildwheel` - I'm pretty...

I guess it wouldn't be too much work to create a subcommand like `--compute-config IDENTIFIER` that returns a human-readable/JSON representation of the config. But, I wonder how generally useful it...

For this second idea, perhaps I'm not following but I wonder if you could append this to your `test-command`? So you do `pytest && gcovr` ?

> I wonder if this issue stems from the fact that `actions/setup-python` makes the `PKG_CONFIG_PATH` environment variable available: https://github.com/actions/setup-python/blob/main/docs/advanced-usage.md#using-update-environment-flag. We could try unsetting it. I'm not totally following why we...

@copilot look into these test failures