homepage

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 pitrou
Recipients belopolsky, ethan.furman, mark.dickinson, pitrou, serhiy.storchaka, skrah, terry.reedy
Date 2015年04月27日.19:02:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1430161334.13.0.213021883262.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.
> I want discourage people from using computed integer results as exit status.
Ok, that's the first good argument for this feature. Although I would encourage people raise an exception if they want to signify a failure, rather than simply change the error code.
History
Date User Action Args
2015年04月27日 19:02:14pitrousetrecipients: + pitrou, terry.reedy, mark.dickinson, belopolsky, skrah, ethan.furman, serhiy.storchaka
2015年04月27日 19:02:14pitrousetmessageid: <1430161334.13.0.213021883262.issue24053@psf.upfronthosting.co.za>
2015年04月27日 19:02:14pitroulinkissue24053 messages
2015年04月27日 19:02:14pitroucreate

AltStyle によって変換されたページ (->オリジナル) /