MouseTrap Pylint Work
Contents
MouseTrap's code quality is important to everyone and to keep it in a high level MouseTrap uses Logilab's pylint and the Orca's run_pylint.sh script. See Orca/Pylint
bash-3.2$ pylint --version pylint 0.18.0, astng 0.19.0, common 0.39.0 Python 2.6.1 (r261:67515, Dec 7 2008, 18:56:39) [GCC 4.3.2]
You can get the latest pylint code here:
logilab-common - common code (prereq)
logilab-astng - abstract syntax tree next generation (prereq)
pylint - pylint itself
The general pattern to install these is to unpack the sources, go into the directory, and then do a python setup.py build followed by a python setup.py install.
The goal is to make every file have a rating of 10 using this pylintrc file. Before checking in their code, each team member should run pylint on the modules they've changed. The top level directory in the MouseTrap sources contains a run_pylint.sh script to help you with this -- it will find the files you've changed and run pylint on just them. In order for this to work, however, you need to first have done a make install in your MouseTrap development area:
./run_pylint.sh
If you want to run pylint on its own, here's an example command, assuming your MouseTrap modules were installed under /usr/lib/python2.6/site-packages:
pylint --init-hook="import pyatspi" \ /usr/lib/python2.6/site-packages/mousetrap/ui/main.py