feat: Include abiflags in version dectection (enabling 3.13t) #199
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.
Description
Currently, you can install free-threaded Python in GitHub actions (with deadsnakes or uv), and have
tox.ini
contain:But the version is detected as
3.13
, since only the version information is considered, not the abiflags. This enables abiflags, which in turn enables this use case.This is important for setting conditions in tox that only apply to free-threading builds, such as setting
PYTHONGIL=0
or limiting dependencies to those withpy3
orcp313t
wheels.You can see it in action in https://github.com/nipy/nibabel/actions/runs/12217554525/job/34081969908:
Expected Behavior
When detecting a matching Python, 3.13t will be tried before falling back to 3.13 and 3.