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 martin.panter
Recipients belopolsky, berker.peksag, mark.dickinson, martin.panter, pitrou, scoder, serhiy.storchaka, skrah, terry.reedy
Date 2015-07-22.02:49:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
FWIW I have wondered in the past why these constants were missing. I would be more likely to use them when checking an exit status than when setting one. I typically do “raise SystemExit()” or “raise SystemExit('Error message')”, which implicitly sets the status.

My preference would be to put EXIT_SUCCESS and EXIT_FAILURE in the “os” module, next to the existing EX_ codes. But I guess the “sys” module would also work.
Date User Action Args
2015-07-22 02:49:06martin.pantersetrecipients: + martin.panter, terry.reedy, mark.dickinson, belopolsky, pitrou, scoder, skrah, berker.peksag, serhiy.storchaka
2015-07-22 02:49:06martin.pantersetmessageid: <>
2015-07-22 02:49:06martin.panterlinkissue24053 messages
2015-07-22 02:49:06martin.pantercreate