Message394174
Hello,
It looks like when asyncio sets up a signal handler, it forgets about the previous one (if any).
Here's a patch (was about to create a PR but the default text brought me to bugs.python.org)
https://github.com/franciscod/cpython/commit/bdac885b86fbb01d0d775f40c47870e48af5fa5b
Tracked this down to the initial asyncio checkout, in commit 27b7c7ebf1039e96cac41b6330cf16b5632d9e49, a few commits before v3.4.0a4.
Not sure if this is a bug but it surprised me. I would have expected that it registered an "additional" signal handler, or at least that my previously installed signal handler would be called afterwards.
Also I'm not sure that it's a good idea to suddenly start running handlers that some current code might rely on not running, or have worked around this behaviour otherwise.
Thanks,
Francisco |
|
Date |
User |
Action |
Args |
2021-05-22 03:09:03 | Francisco Demartino | set | recipients:
+ Francisco Demartino, asvetlov, yselivanov |
2021-05-22 03:09:03 | Francisco Demartino | set | messageid: <1621652943.28.0.466235742077.issue44212@roundup.psfhosted.org> |
2021-05-22 03:09:03 | Francisco Demartino | link | issue44212 messages |
2021-05-22 03:09:02 | Francisco Demartino | create | |
|