What is the thinking behind the PyGTK GC mechanism? I've looked at the
code but don't think that I understand it. What I see is that PyGTK
widgets that are GObjects are viewed as Python containers and the Python
GC system is used to track and presumably dispose of them. It seems that
PyGTK objects are not GC'd if they have a GTK reference which keeps
alive unreferenced (in Python) widgets that are added to a GTK
container. What other things am I missing in understanding the PyGTK
memory management?
As Thomas Leonard points out there is a problem with handling cyclic
references involving signal handler closures that reference the Python
object. Are there other problems?
Thanks
John
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
- Re: [pygtk] Compiling PyGTK2 joehill
- Re: [pygtk] Compiling PyGTK2 Christian Reis
- Re: [pygtk] Compiling PyGTK2 joehill
- Re: [pygtk] Compiling PyGTK2 Christian Reis
- Re: [pygtk] Compiling PyGTK2 Thomas Leonard
- Re: [pygtk] Compiling PyGTK2 Christian Reis
- Re: {SPAM?} Re: [pygtk] Compiling PyGTK2 Thomas Leonard
- Re: [pygtk] Compiling PyGTK2 Johan Dahlin
- Re: [pygtk] Compiling PyGTK2 Ava Arachne Jarvis
- Re: [pygtk] Compiling PyGTK2 joehill
- John Finlay
