Message333765
| Author | jdemeyer |
|---|---|
| Recipients | flox, jdemeyer, martin.panter, neologix, njs, petri.lehtinen, pitrou, r.david.murray, rpcope1, takluyver, vilya, vstinner |
| Date | 2019-01-16.13:00:49 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1547643650.04.0.327216212872.issue13285@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> In Jeroen's API, I can see what the Python-level signal handler is, but there's no way to find out whether that signal handler is actually in use or not. I added support for that in the latest cysignals release. Now you can do >>> import signal >>> from cysignals.pysignals import getossignal, python_os_handler >>> _ = signal.signal(signal.SIGINT, signal.default_int_handler) >>> getossignal(signal.SIGINT) == python_os_handler True Note that cysignals is POSIX-only for now (it assumes sigaction), but the code could easily be ported to other systems. Ideally it would become part of CPython's signal module. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-01-16 13:00:51 | jdemeyer | set | recipients: + jdemeyer, pitrou, vstinner, vilya, r.david.murray, njs, flox, neologix, takluyver, petri.lehtinen, martin.panter, rpcope1 |
| 2019-01-16 13:00:50 | jdemeyer | set | messageid: <1547643650.04.0.327216212872.issue13285@roundup.psfhosted.org> |
| 2019-01-16 13:00:50 | jdemeyer | link | issue13285 messages |
| 2019-01-16 13:00:49 | jdemeyer | create | |