Don't emit 'Couldn't import C tracer' warning for 3.13t - #2203
Merged
nedbat merged 1 commit intoJun 22, 2026
Merged
Conversation
Member
|
I was trying to think of a way to test this, but the wheels are created late, and not in a place that has all the Python versions. |
nedbat
added a commit
that referenced
this pull request
Jun 22, 2026
Member
|
This is now released as part of coverage 7.14.3. |
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
2 participants
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.
coverage.py 7.14.2 no longer has 3.13t wheels, and so falls back to the Python tracer and gives this warning:
For example, https://github.com/prettytable/prettytable/actions/runs/27951172985/job/82708177859 with pytest config promoting warnings to errors.
The warning is only meant to be emitted when wheels are shipped, so update the constant.
However, we can't use the existing:
because it's possible for the GIL can be re-enabled in a free-threaded build, so check for a free-threaded build instead: