Joe Rickerby
Joe Rickerby
`platform.machine()` is the standard way that cibuildwheel does it.
Oh, you want this to support cross-builds. Simplest thing would be to check the _PYTHON_HOST_PLATFORM env var, and fall back to `platform.machine()` if it's not set. See cibuildwheel/macos.py for values....
Yep. Though I think that detail echos what most build backends would do, too?
We could add a note to the FAQ around this area - https://cibuildwheel.readthedocs.io/en/stable/faq/#how-to-cross-compile "Detecting the target architecture when cibuildwheel is cross-compiling" - noting the _PYTHON_HOST_PLATFORM mechanism and the `sysconfig.get_platform()` method....
+1 to all Henry said. Just a little note on terminology- > Is a call to `sysconfig.get_platform` going to return the target architecture, or the host architecture? It'll return the...
If I'm reading the linked issue right, it seems that this problem is localised to CPython 3.8? In a way, I'm not surprised. The universal2/arm64 support in that installer has...
> This was tricky to add, but it was extremely important - 3.8 was the default version of Python on macOS 11! So anyone using the system Python on macOS...
Thanks for the analysis @henryiii > I think we could start by checking to see if the resolved macOS archetectures includes U2. If not, then we replace the Intel URL...
PR welcome!
> This seems like a bigger change that should sit in main a bit, but we are well past due on a a release with the latest PyPy Apologies, I...