-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add linux_aarch64
platform
#76
Add linux_aarch64
platform
#76
Conversation
@christianbundy @hauntsaninja Now we have native arm64 GitHub Actions runners for Ubuntu and Windows. |
Hello, is this closer to being merged? Thank you! |
Looking at the PyPI download stats, I also think it would make sense to add wheels for It's a bit unfortunate that the build takes so much longer than any of the other platforms. Maybe we should only build When Github finally makes ARM runners available for free plans as well, we could reconsider that. github/roadmap#970 pypinfo -pc --days 28 --all --limit 20 \
--where 'details.cpu != "None"' 'mypy==1.13.*' system cpu libc
|
Thanks for the data. It does look like the musllinux aarch64 wheels are over two hours, which is much slower than even the manylinux aarch64 wheels, and benefits 0.00% of users. Pushed a commit dropping them. After that, we can merge and see. Worst case we revert and wait for Github to ship ARM runners. |
Good call, thanks! Looking forward to checking out the impact here. |
Mypy |
Finally!!!! 🎉 |
Problem
We aren't building wheels for
linux_aarch64
, which is a commonly used architecture. For example, when using Docker on an Apple M1 Pro:Solution
Add
aarch64
toCIBW_ARCHS_LINUX
, add QEMU for emulation, and add an override tocibuildwheel.toml
that runs only testcheck. This takes about 90 minutes for manylinux and 2 hours for musllinux.See-also: #37