Re: Event loop documentation error

From	Mark Lawrence <breamoreboy@yahoo.co.uk>
Subject	Re: Event loop documentation error
Date	2014-07-21 20:15 +0100
References	<CAFEUn8agDaOvMzXLv3vGD-5hw=oLmLYGHx31+CO7=Ds-tO8s2w@mail.gmail.com> <CAPTjJmpaUnK_+0v4=4rqQ0JUHAhFsWtvrAhUhCQi3266rZMHrg@mail.gmail.com> <CAFEUn8YSVur3OgJL6D-YcQ_tzakwSDm_9W7d4jjNyVKp36AOXA@mail.gmail.com> <CAFEUn8ZuZ8d+XDyv09bGh3KWUng=Rg7C5_44wh0G6R7PouL2PQ@mail.gmail.com> <CAPTjJmqKgS2jkRvsBDJn=A8exRRXD3uYzrJfHeL5SEnm5NRz_w@mail.gmail.com>
Newsgroups	comp.lang.python
Message-ID	<mailman.12148.1405970077.18130.python-list@python.org> (permalink)

Show all headers | View raw

On 21/07/2014 20:00, Chris Angelico wrote:
> On Tue, Jul 22, 2014 at 4:55 AM, Yaşar Arabacı <yasar11732@gmail.com> wrote:
>> After reading the next page of the documentation, I realized that
>> "add_signal_handler() and remove_signal_handler() are not supported"
>> on Windows. Moreover, dev3.5 version of the docs are also saying that
>> they are not supported, so I think they are not planning to supports
>> those features on Windows anytime soon.
>
> If I had to guess, I would say that the reason there's no Windows
> Ctrl-C handler would simply be that nobody's yet volunteered to write
> one. So you might be in a position to add what you want to 3.5 :)
>
> ChrisA
>

I'd check the bug tracker before doing anything.  It's perfectly 
possible that somebody has already done this but the patch hasn't been 
reviewed yet.

-- 
My fellow Pythonistas, ask not what our language can do for you, ask 
what you can do for our language.

Mark Lawrence

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com

Back to comp.lang.python | Previous | Next | Find similar | Unroll thread

Thread

Re: Event loop documentation error Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-21 20:15 +0100

csiph-web