[3.14] change in behaviour in gc.get_referrers(some_local)
未关闭
@markshannon 已经在做这个了。
开始于 2024年10月16日。
3.14
triaged
type-bug
- 主要语言
- Python
- 星标
- 77.2k
- 派生
- 35.9k
- PR 合并指标
- PR 指标待抓取
描述
Bug report
Bug description:
import gc
async def demo():
class A:
pass
a = A()
print(gc.get_referrers(a))
try:
demo().send(None)
except StopIteration as e:
print(f"{e.value=}")
on 3.11-3.13 this prints:
[]
e.value=None
on 3.14 this prints:
[<coroutine object demo at 0x7d00fff85000>]
e.value=None
this makes gc.get_referrers less useful in detecting cyclic garbage where I'd like to be able to make the assertion that the current frame is the only referrer to an Exception.
the alternative is to hold a weak reference to the object, delete the object and see if the weak reference is dead with the gc disabled. But then I don't get any debug information in my failing test of why the object is still alive.
CPython versions tested on:
3.14, CPython main branch
Operating systems tested on:
Linux
note: @markshannon asked me to open this issue
Linked PRs
- gh-125640
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
评估
这个 Issue 还没有评估数据。