>>>>> "AMK" == Andrew Kuchling <akuchlin@mems-exchange.org> writes: AMK> On Tue, Jul 11, 2000 at 11:52:05AM -0400, Jeremy Hylton wrote: >obj = poll.new() # generate a new pollfd array >obj.register(f1, POLLIN | POLLOUT) >obj.register(f2, POLLOUT) >obj.poll() >obj.unregister(f2) >obj.poll() AMK> Very interesting, and probably worth doing because all that AMK> list parsing *is* a silly waste of CPU. But could poll still AMK> live in the posixmodule, then, or be a module of its own? [1] The select module has exactly the same problem and could use the same interface. They could both live in their own module. I'm not sure what to call it. Possibilities include: - add it to the current select module - new name, e.g. asyncio, fileevent - call it _asyncore and expose it through the asyncore module Jeremy
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