I made a little script that walks through the parpg code directory and checks for possible code errors using pylint.
Usage:
To check for possible code errors:
parpg_check.py </path/to/parpg>
To check for possible PEP-8 code conventions only:
parpg_check.py --check pep8 </path/to/parpg>
To check for code warnings:
parpg_check.py --check warnings </path/to/parpg>
To check for refactors, aka possible bad code smell:
parpg_check.py --check refactors </path/to/parpg>
And the whole shebang:
parpg_check.py --check all </path/to/parpg>
You need pylint (
http://www.logilab.org/857/) to use the script. Pylint isn't perfect so you might get a couple of false positives, but it is useful for finding simple errors and PEP-8 code violations. Also, the script spits out the messages to stdout, so you might want to redirect it to a file ( parpg_check.py /path/to/parpg > check.txt).
I have not tested in on Windows as I don't have a Windows box, so your mileage may vary there.
octavio
