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 flox
Recipients ezio.melotti, flox, jcea, pitrou
Date 2010-03-03.15:34:08
SpamBayes Score 7.00269e-07
Marked as misclassified No
Message-id <1267630451.26.0.152413773226.issue7808@psf.upfronthosting.co.za>
In-reply-to
Content
> Could you explain the changes to the unittest?

The reference to "self" in the hooks were preventing the GC of the test case, as far as I understand, because it creates a cycle.
When using weak references, there's no more dead cycles.
It is my own explanation, maybe it's not exactly what happens.

For the sys.traceback, I could not explain it better than the FAQ:
http://docs.python.org/faq/design.html#how-does-python-manage-memory

I may add a small comment in test_replication to explain the usage of weakref.
History
Date User Action Args
2010-03-03 15:34:11floxsetrecipients: + flox, jcea, pitrou, ezio.melotti
2010-03-03 15:34:11floxsetmessageid: <1267630451.26.0.152413773226.issue7808@psf.upfronthosting.co.za>
2010-03-03 15:34:09floxlinkissue7808 messages
2010-03-03 15:34:08floxcreate