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 vstinner
Recipients SamB, foom, gregory.p.smith, jwilk, loewis, martin.panter, mwh, petri.lehtinen, pitrou, rnk, vstinner
Date 2019-02-14.00:06:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1550102810.82.0.913551441428.issue1054041@roundup.psfhosted.org>
In-reply-to
Content
> A question that leads to is what _is_ the correct value.

What do you think of using a short test program (ex: uses raise(SIGINT)) in ./configure to get the "default exit code" to define a constant, and then use the constant for exit() in Python?

I dislike the idea of raising signals in general. The exact behavior of signals depends too much on the OS, it's hard to get it right. But having a configurable exit code looks safe and simple enough.
History
Date User Action Args
2019-02-14 00:06:50vstinnersetrecipients: + vstinner, mwh, loewis, gregory.p.smith, foom, pitrou, jwilk, rnk, petri.lehtinen, martin.panter, SamB
2019-02-14 00:06:50vstinnersetmessageid: <1550102810.82.0.913551441428.issue1054041@roundup.psfhosted.org>
2019-02-14 00:06:50vstinnerlinkissue1054041 messages
2019-02-14 00:06:50vstinnercreate