On 06/03/2010 23:37, Greg Ewing wrote: > Phillip J. Eby wrote: >> while at the same time creating yet another alternative (and mutually >> incompatible) event loop system in the stdlib, beyond the ones that >> are already in asyncore, tkinter, and the various SocketServer >> subclasses. > > Aaargh... that's the *last* thing we need! > > I've been thinking for a while that it would be a big help > if there were one, standardised module in the stdlib for > handling async events, and all the other gui toolkits > etc. were made to use it. > Wouldn't it have to be the Tcl event loop then? Michael -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog READ CAREFULLY. By accepting and reading this email you agree, on behalf of your employer, to release me from all obligations and waivers arising from any and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your employer, its partners, licensors, agents and assigns, in perpetuity, without prejudice to my ongoing rights and privileges. You further represent that you have the authority to release me from any BOGUS AGREEMENTS on behalf of your employer.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4