Probably ... I'd suggest thats an inconsistency/bug. Currently bad
options such as --blah will be being handled by optparse and thats
probably the one responsible for returning the value 2 at the moment.
derek.
On 4/11/2009, at 12:26 PM, * wrote:
Thanks, I'm blind. In that case, shouldn't "pylint -blah" exit with
code 32 not 2?
On Tue, Nov 3, 2009 at 1:18 AM, Derek Harland <de...@chocolate-fish.com
> wrote:
This is documented ...
$ pylint --help
...
Output status code:
Pylint should leave with following status code:
* 0 if everything went fine
* 1 if some fatal message issued
* 2 if some error message issued
* 4 if some warning message issued
* 8 if some refactor message issued
* 16 if some convention message issued
* 32 on usage error
status 1 to 16 will be bit-ORed so you can know which different
categories has been issued by analysing pylint output status code
On 3/11/2009, at 4:49 PM, * wrote:
I'm having trouble understanding the exit status of pylint. Could
someone point me to where this is documented (if it is)?
unix> pylint test.py
...
unix> echo $?
16
unix> pylint test.py --disable-msg=C0111
...
unix> echo $?
0
unix> pylint -blah
...
unix> echo $?
2
I'm accustomed to unix programs following the convention of
exiting 0
for success and 1-255 for failure. I'm not clear how to distinguish
failure from the above. Thanks.
_______________________________________________
Python-Projects mailing list
Python-Projects@lists.logilab.org
http://lists.logilab.org/mailman/listinfo/python-projects
_______________________________________________
Python-Projects mailing list
Python-Projects@lists.logilab.org
http://lists.logilab.org/mailman/listinfo/python-projects
