You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[<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.
Bug report
Bug description:
on 3.11-3.13 this prints:
on 3.14 this prints:
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
The text was updated successfully, but these errors were encountered: