This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients gvanrossum, vstinner, yselivanov
Date 2015-07-09.14:10:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1436451012.9.0.143193752985.issue24598@psf.upfronthosting.co.za>
In-reply-to
Content
> 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.
History
Date User Action Args
2015-07-09 14:10:12vstinnersetrecipients: + vstinner, gvanrossum, yselivanov
2015-07-09 14:10:12vstinnersetmessageid: <1436451012.9.0.143193752985.issue24598@psf.upfronthosting.co.za>
2015-07-09 14:10:12vstinnerlinkissue24598 messages
2015-07-09 14:10:12vstinnercreate