Skip to content

Conversation

mhsmith
Copy link
Member

@mhsmith mhsmith commented Aug 21, 2025

  • Add Python 3.14 support, including downloading official binaries from python.org.

  • Simplify update_pythons.py:

    • Remove the redundant Windows arch setting.
    • Unify Config classes which are now identical.
    • Make the new config replace the old config rather than merge with it. This makes the behavior easier to reason about.
  • Update to latest versions of Python 3.13 and 3.14:

    • CPython's android.py script now automatically configures KVM on GitHub Actions, so cibuildwheel users no longer need to do that manually.
  • Don't assume that patchelf will be on the PATH (#2552).

@henryiii
Copy link
Contributor

FYI, if it helps at all, currently we just read the groups out and pass them as requirements, but we can probably move to using the --groups option at some point now that pip and uv support it.

@mhsmith mhsmith marked this pull request as ready for review August 22, 2025 21:30
@mhsmith
Copy link
Member Author

mhsmith commented Aug 22, 2025

There are a few more things I want to deal with, but they're all connected to testing wheels, so I think I'll put them in a separate PR.

@mhsmith mhsmith requested a review from henryiii August 22, 2025 21:34
@henryiii
Copy link
Contributor

Should we consider this the start of 3.2?

@mhsmith
Copy link
Member Author

mhsmith commented Aug 26, 2025

I'm not exactly sure what the version number policy is. There's nothing backward incompatible about this PR, but it does add a new platform / Python version pair.

@joerick
Copy link
Contributor

joerick commented Aug 30, 2025

Examples test run

Branch: example-config-test---android-2025-08-2025-08-30T18-48-50

Service Config Status
github examples/github-deploy.yml Build

Generated by bin/run_example_ci_config.py

Copy link
Contributor

@joerick joerick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. I'll have a look at the other PRs regarding the versioning question...

@joerick
Copy link
Contributor

joerick commented Aug 30, 2025

The current PR queue feels like we're heading to 3.2 at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants