-
Notifications
You must be signed in to change notification settings - Fork 277
feat: Python 3.14rc1 build by default #2507
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
Merged
Merged
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,53 +1,53 @@ | ||
| [x86_64] | ||
| manylinux2014 = quay.io/pypa/manylinux2014_x86_64:2025.07.20-2 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_x86_64:2025.07.20-2 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_x86_64:2025.07.20-2 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_x86_64:2025.07.20-2 | ||
| manylinux2014 = quay.io/pypa/manylinux2014_x86_64:2025.07.23-1 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_x86_64:2025.07.23-1 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_x86_64:2025.07.23-1 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_x86_64:2025.07.23-1 | ||
|
|
||
| [i686] | ||
| manylinux2014 = quay.io/pypa/manylinux2014_i686:2025.07.20-2 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_i686:2025.07.20-2 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_i686:2025.07.20-2 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_i686:2025.07.20-2 | ||
| manylinux2014 = quay.io/pypa/manylinux2014_i686:2025.07.23-1 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_i686:2025.07.23-1 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_i686:2025.07.23-1 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_i686:2025.07.23-1 | ||
|
|
||
| [aarch64] | ||
| manylinux2014 = quay.io/pypa/manylinux2014_aarch64:2025.07.20-2 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_aarch64:2025.07.20-2 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_aarch64:2025.07.20-2 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_aarch64:2025.07.20-2 | ||
| manylinux2014 = quay.io/pypa/manylinux2014_aarch64:2025.07.23-1 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_aarch64:2025.07.23-1 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_aarch64:2025.07.23-1 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_aarch64:2025.07.23-1 | ||
|
|
||
| [ppc64le] | ||
| manylinux2014 = quay.io/pypa/manylinux2014_ppc64le:2025.07.20-2 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_ppc64le:2025.07.20-2 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_ppc64le:2025.07.20-2 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_ppc64le:2025.07.20-2 | ||
| manylinux2014 = quay.io/pypa/manylinux2014_ppc64le:2025.07.23-1 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_ppc64le:2025.07.23-1 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_ppc64le:2025.07.23-1 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_ppc64le:2025.07.23-1 | ||
|
|
||
| [s390x] | ||
| manylinux2014 = quay.io/pypa/manylinux2014_s390x:2025.07.20-2 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_s390x:2025.07.20-2 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_s390x:2025.07.20-2 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_s390x:2025.07.20-2 | ||
| manylinux2014 = quay.io/pypa/manylinux2014_s390x:2025.07.23-1 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_s390x:2025.07.23-1 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_s390x:2025.07.23-1 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_s390x:2025.07.23-1 | ||
|
|
||
| [pypy_x86_64] | ||
| manylinux2014 = quay.io/pypa/manylinux2014_x86_64:2025.07.20-2 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_x86_64:2025.07.20-2 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_x86_64:2025.07.20-2 | ||
| manylinux2014 = quay.io/pypa/manylinux2014_x86_64:2025.07.23-1 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_x86_64:2025.07.23-1 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_x86_64:2025.07.23-1 | ||
|
|
||
| [pypy_i686] | ||
| manylinux2014 = quay.io/pypa/manylinux2014_i686:2025.07.20-2 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_i686:2025.07.20-2 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_i686:2025.07.20-2 | ||
| manylinux2014 = quay.io/pypa/manylinux2014_i686:2025.07.23-1 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_i686:2025.07.23-1 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_i686:2025.07.23-1 | ||
|
|
||
| [pypy_aarch64] | ||
| manylinux2014 = quay.io/pypa/manylinux2014_aarch64:2025.07.20-2 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_aarch64:2025.07.20-2 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_aarch64:2025.07.20-2 | ||
| manylinux2014 = quay.io/pypa/manylinux2014_aarch64:2025.07.23-1 | ||
| manylinux_2_28 = quay.io/pypa/manylinux_2_28_aarch64:2025.07.23-1 | ||
| manylinux_2_34 = quay.io/pypa/manylinux_2_34_aarch64:2025.07.23-1 | ||
|
|
||
| [armv7l] | ||
| manylinux_2_31 = quay.io/pypa/manylinux_2_31_armv7l:2025.07.20-2 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_armv7l:2025.07.20-2 | ||
| manylinux_2_31 = quay.io/pypa/manylinux_2_31_armv7l:2025.07.23-1 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_armv7l:2025.07.23-1 | ||
|
|
||
| [riscv64] | ||
| manylinux_2_39 = quay.io/pypa/manylinux_2_39_riscv64:2025.07.20-2 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_riscv64:2025.07.20-2 | ||
| manylinux_2_39 = quay.io/pypa/manylinux_2_39_riscv64:2025.07.23-1 | ||
| musllinux_1_2 = quay.io/pypa/musllinux_1_2_riscv64:2025.07.23-1 | ||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if there was any discussion about it already. Should
cp314treally be build by default? I'm not involved enough in the free threading ecosystem to know the current state of things. At least for mypy, I'd probably need to disable the builds manually to get the build pipeline to pass if the PR is merged as is.The
enable = ["cpython-freethreading"]option feels safer at least for the moment.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Starting with CPython 3.14 beta 3, free-threading is no longer experimental. That means every package should strive to produce free-threading wheels, and they should opt out rather than opt in, unlike 3.13. We only had the enable while it was experimental ("This will enable building these wheels while they are experimental." was the exact quote in our docs). We turned this off in a previous PR #2503, and that’s where you can see the text about this only being true while experimental. https://peps.python.org/pep-0779/
I think it's fine if you have to turn it off, you are explicitly stating you don't fully support all of 3.14. Most binding tools (pybind11, nanobind, cython, SWIG, PyO3, see https://py-free-threading.github.io/tracking/) have supported free threading for quite a while. MyPyC is one of the largest ones that doesn't, I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also see https://www.python.org/downloads/release/python-3140b3/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I did see that it's no longer considered experimental. Though I'd say that mainly applies for cpython itself. Not sure how far along the ecosystem itself is / how challenging it is to get the free threading builds to pass.
I'd suspect this will probably take another year or two, at least.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but hopefully this will push people to start supporting it if they aren't already. The next stage will require most packages to support it, and I think the point of declaring it no longer experimental upstream is to signal that you can't just ignore it anymore downstream, which is also what we are also doing by requiring it to be explicitly skipped. Plus we explicitly said the enable was only going to be valid while it was experimental upstream. :)
We used to require PyPy be explicitly skipped, and we still require musllinux to be explicitly skipped, so we have a bit of a history of requiring skips. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Getting free threading working hasn't been that bad, though mostly people like @ngoldbaum and @colesbury have done a hero's share of the work, so maybe I shouldn't claim anything about how hard it was. ;) I'd guess it's not that bad for MyPyC, especially if you just supported 3.14t+, which is a little easier.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'd love to chat about adding support for free-threading in MyPyC.
I did the lion's share of the work for NumPy and PyO3 and our team has been involved in updating Cython, CFFI, SWIG and many other packages across the ecosystem. There's also the guide we're maintaining at https://py-free-threading.github.io.
All that to say we've accumulated a fair bit of know-how for this and we'd very much like to help out with MyPyC. In almost all cases we've looked at so far the issues have been more tractable than people initially feared.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I suspected at least for mypy there were quite a few build errors. This is just from a test run: https://github.com/cdce8p/mypy_mypyc-wheels/actions/runs/16496179019/job/46642337801#step:4:4390.
This isn't my area of expertise per se. Feel free to engage on the issue tracker though. I believe this is the relevant issue for it: mypyc/mypyc#1038.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To add one more datapoint only because I saw it just now: The dependabot update compatibility for cibuildwheel is at 33% currently. Obviously it's difficult to tell if that's because of 314, free threading or a combination of both.
Anyway the release notes make it quite obvious how to disable it so it isn't really an issue.