Message 155209 - Python tracker

➜

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.

Author	loewis
Recipients	loewis, nadeem.vawda, neologix, pitrou
Date	2012-03-09.07:14:34
SpamBayes Score	2.8545173e-07
Marked as misclassified	No
Message-id	<1331277275.14.0.703518261811.issue14229@psf.upfronthosting.co.za>
In-reply-to

Content
I'm not so sure that Python is in violation of the convention here. The exit code should report unhandled signals, indicating that the process didn't provide an exit code at all (as it didn't call exit(2)). You are supposed to use WIFEXITED/WIFSIGNALED/WIFSTOPPED on the status code, and interpret it as an exit code only if WIFEXITED. Since Python does handle the signal, and exits "regularly", we shouldn't (and probably even can't) claim that we didn't exit (unless we raise the signal again instead of exiting).

I'm not so sure that Python is in violation of the convention here. The exit code should report *unhandled* signals, indicating that the process didn't provide an exit code at all (as it didn't call exit(2)). You are supposed to use WIFEXITED/WIFSIGNALED/WIFSTOPPED on the status code, and interpret it as an exit code only if WIFEXITED.

Since Python *does* handle the signal, and exits "regularly", we shouldn't (and probably even can't) claim that we didn't exit (unless we raise the signal again instead of exiting).

History
Date	User	Action	Args
2012-03-09 07:14:35	loewis	set	recipients: + loewis, pitrou, nadeem.vawda, neologix
2012-03-09 07:14:35	loewis	set	messageid: <1331277275.14.0.703518261811.issue14229@psf.upfronthosting.co.za>
2012-03-09 07:14:34	loewis	link	issue14229 messages
2012-03-09 07:14:34	loewis	create