Message102850
| Author | pitrou |
|---|---|
| Recipients | amcnabb, georg.brandl, neologix, pitrou, pts, tim.peters |
| Date | 2010-04-11.16:14:00 |
| SpamBayes Score | 0.0005620681 |
| Marked as misclassified | No |
| Message-id | <1271002443.27.0.655400479927.issue5315@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
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 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-04-11 16:14:03 | pitrou | set | recipients: + pitrou, tim.peters, georg.brandl, amcnabb, pts, neologix |
| 2010-04-11 16:14:03 | pitrou | set | messageid: <1271002443.27.0.655400479927.issue5315@psf.upfronthosting.co.za> |
| 2010-04-11 16:14:01 | pitrou | link | issue5315 messages |
| 2010-04-11 16:14:01 | pitrou | create | |