2009/12/16 Daniel Harding <[email protected]>
> [email protected] wrote:
>
>>
>> When I run pylint through pylint.bat I do not get the return code of
>> pylint.
>> pylint.bat always returns 0
>>
>> Could you please add 'exit(ERRORLEVEL)' after the exit: label to solve
>> this?
>>
>
> This change was made in changeset 75fca2f13e26 and released in pylint
> 0.18.1. However, now anytime pylint is run from a cmd.exe shell on
> Windows, the exit call closes the shell, even if just doing something
> like 'pylint --help'. This makes pylint essentially unusable from the
> Windows command shell.
>
> I appreciate the desire to be able to determine the return code of
> pylint, but I would suggest that this be implemented using a separate
> script rather than introducing a regression into the existing pylint.bat.
>
I've just found this in the Windows help:
C:\>help exit
EXIT [/B] [exitCode]
/B specifies to exit the current batch script instead of
CMD.EXE. If executed from outside a batch script, it
will quit CMD.EXE
Some research shows that this switch exists since windows 2000.
Wouldn't it help in our case?
--
Amaury Forgeot d'Arc
_______________________________________________
Python-Projects mailing list
[email protected]
http://lists.logilab.org/mailman/listinfo/python-projects
