Henry Schreiner

Yes, you are; please remove this line: https://github.com/ARM-DOE/pyart/blob/a54e9547138b1c5dc5d80c36dcab0c479bac32f1/.github/workflows/wheels.yml#L55 Then you'll only build Intel on Intel and Apple Silicon on Apple Silicon. Currently you are building both on both and GHA...

Also, this will break you when you start building for 3.13: https://github.com/ARM-DOE/pyart/blob/a54e9547138b1c5dc5d80c36dcab0c479bac32f1/.github/workflows/wheels.yml#L56C11-L56C35 3.13 requires 10.13+. cibuildwheel will do this for you if you don't force 10.9. I'd make this `auto64`,...

No problem, close if/when it works!

Let's get 3.13.0 in, make a patch release, then I think this will be ready to merge?

Don't necessarily need to remove the allow-prereleases. The only time Python pre-releases is for upcoming Python versions, which you opt-into anyway. Maybe `"3.x"` or version ranges could be confused, but...

(and, 3.13.0 is available AFAICT, it's just not shipped in manifests or runner images yet. But also I'm not talking about merging the instant we release, either ;) )

Should we add a warning to cibuildwheel running on Python 3.8-3.10 stating that the host Python needs to be upgraded to keep working with the next version of cibuildwheel? Unlike...

I wonder if we should avoid mentioning SPEC 0 too much, I’ve been avoiding mentioning it. I believe the idea is that this is a developer tool, and CI and...

I think this works correctly out of the box with `scikit-build-core`. Well, actually it uses a unique tmp dir every time out of the box, but if you set the...

> then maybe better to fix there? That would be good (and why I said we probably could fix it there). IMO `VSCMD_ARG_TGT_ARCH` is likely a good thing to set...