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 berker.peksag
Recipients belopolsky, berker.peksag, ethan.furman, mark.dickinson, pitrou, serhiy.storchaka, skrah, terry.reedy
Date 2015-04-27.19:07:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1430161642.69.0.310796632328.issue24053@psf.upfronthosting.co.za>
In-reply-to
Content
> 1. I find exit(EXIT_FAILURE) much clearer than exit(1). 

    import sys

    exit(sys.EXIT_FAILURE)

or

    import sys

    sys.exit(sys.EXIT_FAILURE)

don't look too clear to me. On the other hand, these constants may helpful to people who came from C world.

> 3. I want discourage people from using computed integer results as exit status.

Adding a FAQ entry or updating sys.exit() documentation would be more suitable to achieve the aim of this item. I wouldn't add two constants to the stdlib because of a bad programming practice.
History
Date User Action Args
2015-04-27 19:07:22berker.peksagsetrecipients: + berker.peksag, terry.reedy, mark.dickinson, belopolsky, pitrou, skrah, ethan.furman, serhiy.storchaka
2015-04-27 19:07:22berker.peksagsetmessageid: <1430161642.69.0.310796632328.issue24053@psf.upfronthosting.co.za>
2015-04-27 19:07:22berker.peksaglinkissue24053 messages
2015-04-27 19:07:22berker.peksagcreate