Python GUIs: Abandoning TkInter and welcoming wxPython?

[Fredrik Lundh]

Michael P. Reilly wrote:
> Hmm... something about that argument makes it circularly invalid.
> Non-idle event a comes in, but must be handled after idle event d.
> Event d can only execute when event a is taken care of.  Sounds like
> deadlock to me. ;)

hmm.  I thought I'd meant that idle tasks kept piling up
when the windowing system generates a lot of events
at once (like when you're redrawing an entire system).
instead of redrawing everything at once, Tkinter waits
until the window event queue is empty...

</F>