Message157160
| Author | vstinner |
|---|---|
| Recipients | docs@python, neologix, smarnach, vstinner |
| Date | 2012-03-30.23:41:19 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1333150880.38.0.0184594314582.issue14456@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> These two passages are in contradiction to each other. By default, a thread signal can receive any signal and the signal handler implemented in C will be called in the context of the thread. CPython ensures that a signal handler implemented in Python and installed by signal.signal() will be called in the main thread. It uses a signal handler implemented in C which only store the notification and will be the Python signal handler later (as early as possible). pthread_sigmask() can be used to mask some signals (or all signals) on a specific thread. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-03-30 23:41:20 | vstinner | set | recipients: + vstinner, neologix, docs@python, smarnach |
| 2012-03-30 23:41:20 | vstinner | set | messageid: <1333150880.38.0.0184594314582.issue14456@psf.upfronthosting.co.za> |
| 2012-03-30 23:41:19 | vstinner | link | issue14456 messages |
| 2012-03-30 23:41:19 | vstinner | create | |