On Sat, Mar 06, 2004 at 03:51:39PM +0800, Andy Sy wrote:
> Having to do:
>
> connect('signal', lambda w: gtk.main_quit() )
>
> or
>
> self.connect('signal', lambda w,x: gtk.main_quit() )
Note you could use lambda *x: gtk.main_quit() here.
> seems like an ugly hack.
>
> Using:
>
> connect('signal', gtk.mainquit)
>
> would be the most easily understandable.
I've been discussing this with Gustavo on IRC. I'm not sure about this
personally, but I do grant your points that having to wrap main_quit in
another function just to allow it to be connected to signals is a bit
awkward and breaks 'conceptual compatibility' with mainquit.
The fact is that mainquit is an inappropriate name (according to the
platform's naming standard) and that main_quit is what it should be.
However, the issue as to whether it should ignore args supplied to it or
not is still up in the air; I suggest you open a bug on the pygtk
product so we can discuss this further over there (and avoid your valid
complaint to be forgotten in a mailing list message).
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/
