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, berker.peksag, ethan.furman, mark.dickinson, pitrou, scoder, serhiy.storchaka, skrah, terry.reedy
Date 2015-04-27.19:35:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1430163310.22.0.83235122043.issue24053@psf.upfronthosting.co.za>
In-reply-to
Content
>  will confuse inexperienced users when they unexpectedly encounter with sys.exit(sys.EXIT_FAILURE) instead of sys.exit(1).

Are you serious?  I've seen senior programmers who thought that status < 0 means failure and status >= 0 means success.  Why would anyone who understands English would need to know what the numerical value of EXIT_FAILURE is to understand that status=EXIT_FAILURE means "failure"?


Not to mention that google returns a pageful of relevant links for "EXIT_FAILURE".
History
Date User Action Args
2015-04-27 19:35:10belopolskysetrecipients: + belopolsky, terry.reedy, mark.dickinson, pitrou, scoder, skrah, ethan.furman, berker.peksag, serhiy.storchaka
2015-04-27 19:35:10belopolskysetmessageid: <1430163310.22.0.83235122043.issue24053@psf.upfronthosting.co.za>
2015-04-27 19:35:10belopolskylinkissue24053 messages
2015-04-27 19:35:10belopolskycreate