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 belopolsky
Recipients belopolsky, ethan.furman, mark.dickinson, serhiy.storchaka, skrah, terry.reedy
Date 2015-04-24.17:34:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Where are EXIT_FAILURE and EXIT_SUCCESS defined?

In C stdlib:

$ grep EXIT_ /usr/include/stdlib.h
#define	EXIT_FAILURE	1
#define	EXIT_SUCCESS	0

> we should probably call them EX_FAILURE and EX_SUCESS to match what's already there.

No. EX_ macros come from a non-standard sysexits.h header.  Python stdlib traditionally does not change the spelling of the constants that
come from C libraries or standards.

Even in the absence of POSIX and C99 standards, I would prefer EXIT_ prefix over EX_ for clarity.  "EX" does not clearly mean "exit", it may stand for "exception", "execution", "example" etc.
Date User Action Args
2015-04-24 17:34:02belopolskysetrecipients: + belopolsky, terry.reedy, mark.dickinson, skrah, ethan.furman, serhiy.storchaka
2015-04-24 17:34:02belopolskysetmessageid: <>
2015-04-24 17:34:02belopolskylinkissue24053 messages
2015-04-24 17:34:01belopolskycreate