On Sun, 30 Jul 2006 09:50:36 -0700, Josiah Carlson <[EMAIL PROTECTED]> wrote: > >Jean-Paul Calderone <[EMAIL PROTECTED]> wrote: >> >> On Sat, 29 Jul 2006 14:38:38 -0700, Josiah Carlson <[EMAIL PROTECTED]> 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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
