On Tue, Dec 31, 2002 at 11:44:06AM +0100, Arjan J. Molenaar wrote: > leak_references does what it says ;-): leak references. As you know, the > TreeModel makes heavy use of iterators. One of the "not so nice" things > about those iterators is that they get destroyed without any > notification. leak_references == 1 will keep a reference on the Python > object that works as the iterator. This might cause reference count > leaks (and therefore memory leaks). when leak_references == 0, the > Python object that works as the iterator is dereferenced (so it becomes > a weak reference). Problem is that your tree model has to keep track of > the iterators, otherwise you get a segmentation fault. I hope this > explains it a little bit (I'm not in a very explainory mood today ;-).
Thanks for the further explanation. I've added a FAQ entry on this: http://www.async.com.br/faq/pygtk/index.py?req=all#13.20 Dave _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
