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 handle reference cycles. Being aware of the cycles help the developer to control when objects are deleted. It mean breaking the cycles help to delete objects sooner. See other asyncio issues about "reference cycles" for some examples. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24598> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
