[New-bugs-announce] [issue44212] asyncio overrides signal handlers

Francisco Demartino report at bugs.python.org
Fri May 21 23:09:03 EDT 2021

New submission from Francisco Demartino <demartino.francisco at gmail.com>:


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)

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.


components: asyncio
messages: 394174
nosy: Francisco Demartino, asvetlov, yselivanov
priority: normal
severity: normal
status: open
title: asyncio overrides signal handlers
type: behavior
versions: Python 3.10, Python 3.11, Python 3.6, Python 3.7, Python 3.8, Python 3.9

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list