[Python-ideas] asyncore: included batteries don't fit
Guido van Rossum
guido at python.org
Fri Oct 12 02:34:33 CEST 2012
On Thu, Oct 11, 2012 at 5:29 PM, Terry Reedy <tjreedy at udel.edu> wrote:
> On 10/11/2012 5:18 PM, Guido van Rossum wrote:
>> Anyway, it would be good to have input from representatives from Wx,
>> Qt, Twisted and Tornado to ensure that the *functionality* required is
>> all there (never mind the exact signatures of the APIs needed to
>> provide all that functionality).
> And of course tk/tkinter (tho perhaps we can represent that). It occurs to
> me that while i/o (file/socket) events can be added to a user (mouse/key)
> event loop, and I suspect that some tk/tkinter apps do so, it might be
> sensible to keep the two separate. A master loop could tell the user-event
> loop to handle all user events and then the i/o loop to handle one i/o
> event. This all depends on the relative speed of the handler code.
You should talk to a Tcl/Tk user (if there are any left :-). They
actually really like the unified event loop that's used for both
widget events and network events. Tk is probably also a good example
of a hybrid GUI system, where some of the callbacks (e.g. redraw
events) are implemented in C.
--Guido van Rossum (python.org/~guido)
More information about the Python-ideas