This repository was archived by the owner on Aug 30, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 21
Move to github actions #116
Comments
Should we just do that if and when GitHub Actions gets 3.10? Until that time it's just busywork right? Another consideration is doing the same as on the main repo, if we have Windows only on Azure in main CI, then we may want to be careful about building wheels on GHA. |
rgommers
added a commit
to rgommers/oldest-supported-numpy
that referenced
this issue
Aug 18, 2021
There are now Linux `x86_64` and aarch64 wheels up for 1.21.2, and the sdist should work for other platforms (wheels will follow, some infra issues to resolve first - see MacPython/numpy-wheels#116)
GitHub Actions has supported the releases since a1 and so has azure-pipelines (for linux). The tricky bit will be support on Windows and Mac. We could try GitHub Actions for that just to see if it works. |
Closing. Hopefully we will be building wheels on the numpy/numpy repo. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be nice to be able to use the newest python versions to build wheels. For linux, these are available via the manylinux wheels, which are updated pretty quickly after a python release. But for windows and macOS, we need python executables via the CI. Azure tends to lag behind github actions, so perhaps we should move the CI builds to github actions before the release of Python 3.10
The text was updated successfully, but these errors were encountered: