On Thu, Feb 12, 2004 at 01:34:00PM -0600, Liza Klerck wrote:
> I would like to submit a patch for the memory leak problem but am still
> quite a newbie at all of this and am not sure how to go about it ?
Everybody's a newbie at least once. It's easy. Look at FAQ 1.6 and in
particular FAQ 1.16:
http://www.async.com.br/faq/pygtk/index.py?req=show&file=faq01.006.htp
http://www.async.com.br/faq/pygtk/index.py?req=show&file=faq01.016.htp
Basically:
a) File a bug against the pygtk product in the Gnome Bugzilla at
http://bugzilla.gnome.org/
b) Produce a patch (using "diff -urNp") against the original sources
(it helps if you have a CVS pull of pygtk, which you can get by
following FAQ 1.3
http://www.async.com.br/faq/pygtk/index.py?req=show&file=faq01.003.htp
-- then all you need to do is "cvs diff -urNp > my-patch" and
that's it). Attach the patch to the bug.
c) I or someone (nudge nudge J) will look at it, merge the patch,
and send you many messages of eternal gratitude (and
encouragement for more patches), etc etc.
Thanks a lot for tracking this down! I asked Gustavo earlier today and
he suggested the same fix -- you just beat us to it. :-)
Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
