Build macOS architectures separately for CI and wheels

[swt2c]

Building the architectures separately allows them to be built in parallel, which will speed up CI but also result in smaller wheels which should be more efficient instead of universal wheels.

[echoix]

I was exploring at the end of this afternoon to see how easy it would be to use cibuildwheel to use a standardized environment (standardized in the sense that it is common to lots of big and widely used packages).

I can't conclude anything for now

[swt2c]

I was exploring at the end of this afternoon to see how easy it would be to use cibuildwheel to use a standardized environment (standardized in the sense that it is common to lots of big and widely used packages).

I can't conclude anything for now

I think we'd need to get pyproject.toml builds working completely, though, right? When I've used cibuildwheel in other projects, I believe it expects to be able to use build, which doesn't work currently.

[echoix]

I was exploring at the end of this afternoon to see how easy it would be to use cibuildwheel to use a standardized environment (standardized in the sense that it is common to lots of big and widely used packages).
I can't conclude anything for now

I think we'd need to get pyproject.toml builds working completely, though, right? When I've used cibuildwheel in other projects, I believe it expects to be able to use build, which doesn't work currently.

Maybe... and the build is problematic, as normally everyone would use python -m build, but we need to have the repo's root on path, and we have a file named build that gets called instead of the tool...

[swt2c]

I was exploring at the end of this afternoon to see how easy it would be to use cibuildwheel to use a standardized environment (standardized in the sense that it is common to lots of big and widely used packages).
I can't conclude anything for now

I think we'd need to get pyproject.toml builds working completely, though, right? When I've used cibuildwheel in other projects, I believe it expects to be able to use build, which doesn't work currently.

Maybe... and the build is problematic, as normally everyone would use python -m build, but we need to have the repo's root on path, and we have a file named build that gets called instead of the tool...

Yep, I ran into those same problems too (and didn't solve them). ;-)

[echoix]

Maybe... and the build is problematic, as normally everyone would use python -m build, but we need to have the repo's root on path, and we have a file named build that gets called instead of the tool...

Yep, I ran into those same problems too (and didn't solve them). ;-)

At least when doing it out of cibw, build also provides a cli script pyproject-build, that doesn't conflict too much. Or I used uv, with uv build/uv build --sdist/uv build --wheel.