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 Kevin Mills
Recipients Kevin Mills, mark.dickinson
Date 2017-02-27.21:00:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1488229216.96.0.927017518424.issue29671@psf.upfronthosting.co.za>
In-reply-to
Content
gc.disable() at the beginning and then analyzing the results of gc.collect() actually does do what I was wanting, thank you.

Reference cycles in and of themselves aren't the problem. It's only a problem if garbage contains reference cycles. In a normal program, a class wouldn't generally ever become garbage, so it wouldn't be a problem.
History
Date User Action Args
2017-02-27 21:00:17Kevin Millssetrecipients: + Kevin Mills, mark.dickinson
2017-02-27 21:00:16Kevin Millssetmessageid: <1488229216.96.0.927017518424.issue29671@psf.upfronthosting.co.za>
2017-02-27 21:00:16Kevin Millslinkissue29671 messages
2017-02-27 21:00:16Kevin Millscreate