test_track_literals depends on a garbage collection
@sergey-miryanov is already working on this.
Since Aug 13, 2026.
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 35.9k
- PR merge metrics
- PR metrics pending
Description
Bug report
_not_tracked_instantly() requires the tuple to be untracked without a collection. This holds for tuples created at run time, but tuple constants are created tracked and are only untracked by _PyTuple_MaybeUntrack(), which is called only from the collector.
$ ./python -c "import gc; print(gc.is_tracked((1,)))"
True
So test_track_literals passes only if a collection happens between importing the module and running the test. Under regrtest it does not:
$ ./python -m test test_tuple -m test_track_literals
AssertionError: True is not false : (1,)
while ./python -m unittest test.test_tuple.TupleTest.test_track_literals passes.
Untracking tuple constants when the code object is created would let the test keep the stronger check.
Linked PRs
- gh-156419
- gh-156423
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.