[issue5315] signal handler never gets called

[Antoine Pitrou]

Antoine Pitrou <pitrou at free.fr> added the comment:

Thanks for the detailed analysis, Charles-François.

> Finally, I think that the documentation should be rephrased:

Yes, I think so.

> Furthermore, under Linux 2.6 and NPTL, getpid() returns the main thread
> PID even from another thread.

Yes, those threads belong to the same process.

But as mentioned, signals are a rather fragile inter-process communication device; just use a specific file descriptor.
And if you still wanna use signals, there's set_wakeup_fd():
http://docs.python.org/library/signal.html#signal.set_wakeup_fd

----------
assignee:  -> georg.brandl
components: +Documentation
nosy: +georg.brandl, pitrou, tim_one
priority:  -> normal
versions: +Python 2.6, Python 2.7, Python 3.1, Python 3.2 -Python 2.4, Python 2.5

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue5315>
_______________________________________