Orca Pylint Work
The Orca team uses Logilab's pylint to help increase the quality of the Orca code. The pylint version in use is as follows:
bash-3.2$ pylint --version pylint 0.13.2, astng 0.17.1, common 0.25.0 Python 2.4.4 (#1, Oct 8 2007, 16:54:43) [C]
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.
Our goal is to make every file have a rating of 10 using our pylintrc file. We've achieved that goal and want to stay there. Before checking in their code, each team member should run pylint on the modules they've changed. The top level directory in the Orca 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 orca development area:
If you want to run pylint on its own, here's an example command, assuming your Orca modules were installed under /usr/lib/python2.5/site-packages:
pylint --init-hook="import pyatspi" \ /usr/lib/python2.5/site-packages/orca/Gecko.py
The information on this page and the other Orca-related pages on this site are distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.