Windows - select.select, timeout and KeyboardInterrupt
Lawrence D'Oliveiro
ldo at geek-central.gen.new_zealand
Sun May 9 05:59:15 EDT 2010
In message <mailman.2769.1273327083.23598.python-list at python.org>,
exarkun at twistedmatrix.com wrote:
> On 07:48 am, ldo at geek-central.gen.new_zealand wrote:
>
>>In message <mailman.2760.1273288730.23598.python-list at python.org>,
>>exarkun at twistedmatrix.com wrote:
>>
>>>This is a good example of why it's a bad idea to use select on
>>>Windows.
>>>Instead, use WaitForMultipleObjects.
>>
>>How are you supposed to write portable code, then?
>
> With WaitForMultipleObjects on Windows, epoll on Linux, kqueue on BSD,
> event completion on Solaris, etc...
>
> Sound like more work than using select() everywhere? Yea, a bit. But
> not once you abstract it away from your actual application code. After
> all, it's not like these *do* different things. They all do the same
> thing (basically) - differently.
Do you understand what “portable” means?
More information about the Python-list
mailing list