[3.14] change in behaviour in gc.get_referrers(some_local)
Abierto
@markshannon ya está trabajando en esto.
Desde el 16/10/2024.
3.14
triaged
type-bug
- Lenguaje dominante
- Python
- Estrellas
- 77.2k
- Forks
- 36k
- Métricas de merge de PR
- Métricas de PR pendientes
Descripción
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
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Evaluación
Este issue todavía no se ha evaluado.