[pygtk] PyGObject leaking?

[Tony Nelson]

At 10:17 PM -0400 4/11/07, Mario Beauchamp wrote:
>Hi folks.
>
>On 4/11/07, Tony Nelson <tonynelson at georgeanelson.com> wrote:
>> >http://openev.svn.sourceforge.net/viewvc/openev/trunk/src/pymod/gvobject.py?revision=6&view=markup
>>
>> Well, the rot may be deeper than that, inside pygobject or pygtk code. ;)
>> (I can't make heads or tails of that code, sorry if I am slandering it.)
>
>Which code? gvobject.py? Anyhoo, it's useless...
>
>> Python will collect objects as soon as they become unreferenced.
>> Immediately.
>
>Well, it turns out it's not immediate. Someone told me that Python 2.4
>does a collect every 700 deallocations (a value than can be tweaked
>with gc.set_threshold, I think). And it makes sense: I see my
>destroyed objects finally being freed when I do other stuff like
>opening a new window. But it's still not fast enough in certain cases.
 ...

I say again:  Python will collect objects as soon as they become
unreferenced.  Immediately.  It has /nothing/ to do with Garbage
Collection.  It is Reference Counting, and it is the standard way that
Python has always reclaimed unused objects, even before there was Cyclic GC.
-- 
____________________________________________________________________
TonyN.:'                       <mailto:tonynelson at georgeanelson.com>
      '                              <http://www.georgeanelson.com/>