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:17:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1430162244.5.0.0273251874899.issue24053@psf.upfronthosting.co.za>
In-reply-to
Content
>> I want people to standardize on status=1 for a generic failure code.

> Why that? Multiple error codes can be used by the same program, depending on the kind of error.

Antoine, please read what I write carefully before disagreeing.  I want "to standardize on status=1 for a **generic** failure code". Cooperating processes can certainly agree on other values for the specific failure modes.

What I really want to avoid is the use of -1 as a generic failure code, because it leads to a rather common error

rc = subprocess.call(..)
if rc < 0:
   raise Error   # never reached!
History
Date User Action Args
2015-04-27 19:17:24belopolskysetrecipients: + belopolsky, terry.reedy, mark.dickinson, pitrou, scoder, skrah, ethan.furman, berker.peksag, serhiy.storchaka
2015-04-27 19:17:24belopolskysetmessageid: <1430162244.5.0.0273251874899.issue24053@psf.upfronthosting.co.za>
2015-04-27 19:17:24belopolskylinkissue24053 messages
2015-04-27 19:17:24belopolskycreate