RetroSearch Browse

Sun Jul 30 19:20:54 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-July/067841.html

On Sun, 30 Jul 2006 09:50:36 -0700, Josiah Carlson <jcarlson at uci.edu> wrote:
>
>Jean-Paul Calderone <exarkun at divmod.com> wrote:
>>
>> On Sat, 29 Jul 2006 14:38:38 -0700, Josiah Carlson <jcarlson at uci.edu> wrote:
>> >
>> >If someone is looking for a project for 2.6 that digs into all sorts of
>> >platform-specific nastiness, they could add actual signal sending to the
>> >signal module (at least for unix systems).
>>
>> Maybe I am missing something obvious, but what is necessary beyond
>> os.kill()?
>
>I note that os.kill() does everything necessary for posix systems.
>I didn't notice that it took an argument for the kind of signal.
>
>A new project for someone: combine all of the methods available to
>Windows into a single function.
>
>> What /would/ be useful is a complete sigaction wrapper, but that's a
>> completely separate topic.
>
>Like atexit, only a stack per signal?

I just mean a complete wrapping of sigaction(2).  In particular, I
need this functionality to properly install a SIGCHLD handler which
does not interfer with various I/O functions by installing the handler
with the SA_RESTART flag, which is not currently possible using the
signal.signal function.

Jean-Paul

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-July/067841.html below:

[Python-Dev] Testing Socket Timeouts patch 1519025