[issue24598] asyncio: add background task detecting reference cycles

STINNER Victor added the comment: I lost track of this issue, so I just close it, sorry. -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue24598] asyncio: add background task detecting reference cycles

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue24598] asyncio: add background task detecting reference cycles

STINNER Victor added the comment: Python 3.4 is able to break reference cycles even if an object part of the cycle has a destructor. See the PEP 442. -- ___ Python tracker ___ __

[issue24598] asyncio: add background task detecting reference cycles

Joshua Harlow added the comment: Out of curiosity what reference cycles can't be broken in various python versions? Is it documented/explained anywhere? -- nosy: +Joshua.Harlow ___ Python tracker _

[issue24598] asyncio: add background task detecting reference cycles

Changes by Martin Panter : -- nosy: +vadmium ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue24598] asyncio: add background task detecting reference cycles

Guido van Rossum added the comment: OK, no problem. (Side comment: Future is being subclassed a lot, so parametrizing its construction may not be so easy.) -- ___ Python tracker

[issue24598] asyncio: add background task detecting reference cycles

STINNER Victor added the comment: > Hm. If the problem is most prominent with 3.3, why mark the issue as 3.6? Well, I plan to implement this feature in "asyncio", so for 3.3-3.6 in fact. > Do you have an implementation already? Nope, it's more a TODO task for myself :-) > Maybe it can be a 3r

[issue24598] asyncio: add background task detecting reference cycles

Guido van Rossum added the comment: Hm. If the problem is most prominent with 3.3, why mark the issue as 3.6? Do you have an implementation already? Maybe it can be a 3rd party package rather than integrated in asyncio debug mode? -- ___ Python trac

[issue24598] asyncio: add background task detecting reference cycles

STINNER Victor added the comment: > Doesn't the cycle-detecting GC handle these? Maybe you are lucky and the GC is able to break the cycle. Maybe you are unlucky and all objects part of the cycle will never be deleted. Python 3.4 is better to handle these cases, but Python 3.3 is worse to hand

[issue24598] asyncio: add background task detecting reference cycles

Guido van Rossum added the comment: Doesn't the cycle-detecting GC handle these? -- ___ Python tracker ___ ___ Python-bugs-list mailin

[issue24598] asyncio: add background task detecting reference cycles

New submission from STINNER Victor: When storing an exception in an asyncio Future object, there is a high risk of creating a reference cycle. In Python 3, exception objects store a traceback object which store frame objects. The problem is that a frame can also have a reference to the excepti