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 serhiy.storchaka
Recipients belopolsky, berker.peksag, ethan.furman, mark.dickinson, pitrou, scoder, serhiy.storchaka, skrah, terry.reedy
Date 2015-04-27.19:19:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1430162379.28.0.591015214585.issue24053@psf.upfronthosting.co.za>
In-reply-to
Content
How often you see EXIT_SUCCESS and EXIT_FAILURE in C code besides GNU tools that should support VMS? And even GNU tools usually use multiple error codes for different kinds of errors.

I think that these constants are rather unusual for C programmers.

I'm only -0 on adding these constants, not -1, because I'm sure they will be never used. But this will add a burden on the documentation and will confuse inexperienced users when they unexpectedly encounter with sys.exit(sys.EXIT_FAILURE) instead of sys.exit(1).
History
Date User Action Args
2015-04-27 19:19:39serhiy.storchakasetrecipients: + serhiy.storchaka, terry.reedy, mark.dickinson, belopolsky, pitrou, scoder, skrah, ethan.furman, berker.peksag
2015-04-27 19:19:39serhiy.storchakasetmessageid: <1430162379.28.0.591015214585.issue24053@psf.upfronthosting.co.za>
2015-04-27 19:19:39serhiy.storchakalinkissue24053 messages
2015-04-27 19:19:39serhiy.storchakacreate