Repository navigation
Conversation
…ailures. Free-threaded 3.15 exercises PEP 803 abi3t paths that neither 3.14t nor 3.15 reach. Several downstream dependencies lack cp315t wheels and fail to build from source (e.g. bcrypt, via fabric/paramiko), so the job is allowed to fail for now. Closes #223 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jaraco
commented
Oct 20, 2026
| continue-on-error: ${{ inputs.python == '3.15' }} | ||
| # and on free-threaded 3.15, where several dependencies (e.g. bcrypt) | ||
| # don't yet build (jaraco/skeleton#223). | ||
| continue-on-error: ${{ startsWith(inputs.python, '3.15') }} |
Owner
Author
There was a problem hiding this comment.
I don't want to conflate these concerns. The reason 3.15 is listed here is because it was a pre-release. It's no longer a pre-release, but I don't want to bump this to 3.16 here; that'll happen in a separate PR.
jaraco
commented
Oct 20, 2026
| # (jaraco/skeleton#222). | ||
| if: >- | ||
| (inputs.python == '3.15' || startsWith(inputs.python, 'pypy')) | ||
| (startsWith(inputs.python, '3.15') || startsWith(inputs.python, 'pypy')) |
Per review, the 3.15 special-casing in test-suite.yml exists because 3.15 was a pre-release, a separate concern from free-threading. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jaraco
changed the title
This was referenced Oct 20, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #223.
Replaces the free-threaded
3.14tentries (all three platforms) with3.15t.3.15tis the first free-threaded build with PEP 803abi3t, which neither3.14tnor3.15reaches.3.15tis blocking. The pre-release handling intest-suite.ymlis left alone; bumping Python versions now that 3.15 is out is a separate PR.Stability assessment
I checked the latest
mainCI on 93 downstream projects that already run3.14t, plus wheel availability and source builds on 3.15.0t:3.14t: about 87 of 93 projects.3.15(with the GIL) is green on 86.abi3twheels. pyyaml, psutil, zstandard and pynacl have no cp315t wheels but build from source.3.15t:bcrypt5.0.0 has no cp315t wheel, and its sdist pins PyO3 0.26, which can't build for 3.15. That affects everything that depends onfabric/paramiko: jaraco.fabric, jaraco.net and recapturedocs.3.14tand likely to carry over: jaraco.home (pyobjc on Linux), jaraco.postgres (psycopg2-binary), configparser (2 test failures).That makes about 6 expected failures. The affected projects can drop or skip
3.15tlocally until their dependencies catch up (e.g. bcrypt shipping 3.15t wheels).🤖 Generated with Claude Code