-
Notifications
You must be signed in to change notification settings - Fork 110
MAINT: add Python 3.14, drop 3.9, fix some CI and build stuff #481
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
Conversation
The windows-latest runner is moving to windows-2025 during September 2025.
Yes, 1.6.0 sounds good to me
I definitely trust your judgment here, you have way more experience with this. I was a user of macports, which tries to keep things going for old macs, but not having infrastructure to compile it on makes it difficult. I guess it's impossible to crosscompile on Mac Arm? |
Apparently that skip selector is not needed anymore with new |
The cross compile part is easy, but shipping binaries without ever running the tests for that build setup feels quite uncomfortable. I'd personally much prefer not to do that. And support across packages will become spotty fairly quickly anyway, so my sense is that soon enough the reliable way to install a set of packages will be to base it on the cutoff date where GitHub support disappeared with https://docs.astral.sh/uv/reference/settings/#exclude-newer
Ah yes, right, |
…ng needed This is a follow-up to pydatagh-481, which moved to cibuildwheel 3.x which removed PyPy from the default set of wheels being built.
…ng needed This is a follow-up to pydatagh-481, which moved to cibuildwheel 3.x which removed PyPy from the default set of wheels being built.
Python 3.14 is in the release candidate stage, meaning this is the time to add 3.14 wheels on PyPI.
Changes:
windows-2019
numpy
upper bound upAlso, two questions @rdbisme:
EDIT: see this CI log for a full set of (passing) wheel builds.