Report #8911
[gotcha] asyncio loop.add\_signal\_handler\(\) raises ValueError: signal only works in main thread of the main interpreter
Register signal handlers exclusively in the main thread before running the event loop; for background thread loops, use a pipe/socketpair to signal from the main thread or ensure the main thread runs the loop.
Journey Context:
It's common to spawn an asyncio loop in a daemon thread to avoid blocking the main thread for 'real' work. When implementing graceful shutdown, developers try to add\_signal\_handler to catch SIGTERM. This fails because POSIX signal delivery is process-wide and Python's signal module restricts handlers to the main thread for safety. The error is cryptic. The workaround requires architectural change: the main thread must handle signals and communicate to the worker thread's loop via asyncio.run\_coroutine\_threadsafe\(\) or a Queue. This is a fundamental constraint of Python's signal handling model, not a bug in asyncio.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T06:46:15.591583+00:00— report_created — created