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 martin.panter
Recipients Arfrever, georg.brandl, loewis, martin.panter, mkc, pitrou, python-dev, rbcollins, steve.dower, terry.reedy
Date 2015-08-26.09:07:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440580062.36.0.283759134162.issue5319@psf.upfronthosting.co.za>
In-reply-to
Content
I guess I like setting the status to 1 because it matches the status already used by the default exception handling, the value when you raise SystemExit("error message"), and the value used for most internal errors. However I did discover that the exit status is 2 if you give Python wrong CLI arguments or there is an OS error opening a script file.

I’m still rather unsure, only weakly in favour of my original proposal. Maybe see if anyone else has an opinion?
History
Date User Action Args
2015-08-26 09:07:42martin.pantersetrecipients: + martin.panter, loewis, georg.brandl, terry.reedy, mkc, pitrou, rbcollins, Arfrever, python-dev, steve.dower
2015-08-26 09:07:42martin.pantersetmessageid: <1440580062.36.0.283759134162.issue5319@psf.upfronthosting.co.za>
2015-08-26 09:07:42martin.panterlinkissue5319 messages
2015-08-26 09:07:42martin.pantercreate