This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: What should happen to signals when the main thread dies?
Type: enhancement Stage:
Components: Interpreter Core Versions: Python 3.2
process
Status: closed Resolution: later
Dependencies: Superseder:
Assigned To: Nosy List: eggy, terry.reedy
Priority: normal Keywords:

Created on 2009-06-01 16:01 by eggy, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
ignore_signals.py eggy, 2009-06-01 16:01 Ignore signals such as SIGINT
Messages (2)
msg88650 - (view) Author: Mark Florisson (eggy) * Date: 2009-06-01 16:01
As signals are only delivered to the main thread, what should happen
when the main thread dies? Currently, the signal mask is not unset in
any other thread, so when the main thread dies, all signals set in the
mask are simply ignored. Perhaps an other thread could be selected as
the main thread?

The accompanied file demonstrates this behavior.
msg109674 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2010-07-09 03:42
I think there has been some discussion of signals, in the last year, on the py-dev list (== gmane.comp.python.devel), which is archived both on the python site and gmane.org. Signals seem to be a somewhat nasty subject.

Since you only raise a question rather than proposing a specific, possible change, I am closing this for now. I suggest you open a discussion on python-list (mirrored as newsgroup gmane.comp.python.general). Perhaps a specific proposal would come from that, perhaps you would find that your idea is impossible.
History
Date User Action Args
2022-04-11 14:56:49adminsetgithub: 50412
2010-07-09 03:42:06terry.reedysetstatus: open -> closed
versions: - Python 2.6, Python 2.5, Python 2.4, Python 3.0, Python 3.1, Python 2.7
nosy: + terry.reedy

messages: + msg109674

resolution: later
2009-06-01 16:01:32eggycreate