Author neologix
Recipients Arfrever, eric.araujo, loewis, nadeem.vawda, neologix, pitrou, rosslagerwall
Date 2012-03-20.18:56:38
SpamBayes Score 1.23668e-06
Marked as misclassified No
Message-id <CAH_1eM33jOzVS26Wr-6pK5YXKHoOz11VgH2Yi=9eDcRbvMqdWA@mail.gmail.com>
In-reply-to <1331420636.67.0.0465453518787.issue14229@psf.upfronthosting.co.za>
Content
I agree with Martin: we really do handle the signal, and as such, the
only way to convey the relevant information to the parent as to which
signal caused the exit would be to re-raise it, which is really ugly
and probably not a good idea.

Processes that want default behavior upon signal reception (so that
they can use WEXITSTATUS(), WCOREDUMP() and friends) can always use
SIG_DFL:

$ python -c "import subprocess, signal, time; p =
subprocess.Popen(['python', '-c', 'import signal;
signal.signal(signal.SIGINT, signal.SIG_DFL); input()']);
time.sleep(1); p.send_signal(signal.SIGINT); print(p.wait())"
-2
History
Date User Action Args
2012-03-20 18:56:39neologixsetrecipients: + neologix, loewis, pitrou, nadeem.vawda, eric.araujo, Arfrever, rosslagerwall
2012-03-20 18:56:38neologixlinkissue14229 messages
2012-03-20 18:56:38neologixcreate