[Python-ideas] Responsive signal handling

Paul Moore p.f.moore at gmail.com
Mon Jun 22 17:53:24 CEST 2015

On 22 June 2015 at 09:42, Devin Jeanpierre <jeanpierreda at gmail.com> wrote:
> On Mon, Jun 22, 2015 at 12:52 AM, Cameron Simpson <cs at zip.com.au> wrote:
>> On 21Jun2015 19:16, Devin Jeanpierre <jeanpierreda at gmail.com> wrote:
>>> This is not possible in general, but it can be made to work for all
>>> blocking operations in the stdlib.
>> Hmm. I'm not sure that you will find this universally so. No, I have no
>> examples proving my intuition here.
> If you fix select, everything else can hypothetically follow, as you
> can run all C functions in another thread and signal the result is
> ready using an fd. (This is my idea for a hacky third-party library.
> It only ruins stack traces!)

This particular approach presumably only works on Unix? (On Windows,
select is not a general signalling operation, it only works for
sockets). Presumably a cross-platform solution would need to use
appropriate OS-native signalling based on the platform?


More information about the Python-ideas mailing list