>> 1- PyGTK wraps GTK+ for Python. Which life-cycle do we follow, GTK's
>> or Python's?
Matt> Both this point and the one below are best answered by the library
Matt> developers, if they are in favour of the idea of course :^) (I
Matt> should make it clear I _use_ pyGTK, I'm not a developer) although
Matt> to me following the GTK lifecycle then the python 'standard'
Matt> version being the stable version at the time of the python release
Matt> would make sense... GTK and PyGTK release cycles seem to be much
Matt> faster than pythons
I haven't used PyGTK enough to know, but is the GTK community's stance on
breakage similar to that in the Python community? If not, simply shipping
with "the stable version" of PyGTK when Python is released may cause more
perceived Python breakage than that community normally expects.
Skip
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
