[3.14] change in behaviour in gc.get_referrers(some_local)
未關閉
@markshannon 已經在處理了。
開始於 2024年10月16日。
3.14
triaged
type-bug
- 主要語言
- Python
- 星號
- 77.2k
- 分支
- 36k
- 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 還沒有評估資料。