[Python-projects] pyLint: Speeding up pyLint

[Jürgen Hermann]

> The code for my current project is mission critical and therefore I am
> running pyLint --errors-only before every commit. This works fine and,
> as I said, has already saved my b*tt a couple of times.
> 
> The only problem with this is that pyLint is comparatively slow. In my
> project, the unit tests take around 5s to run, pyLint takes 20s.

The usual answer to this is using continuous integration, e.g. Hudson. Besides making the manual steps involved redundant, it also offers other reports via its web interface and emails interested parties about problems.

Python projects have automatic api docs, test & pylint reports, svn change history & last build artifact here. Also building in a non-developer environment means catching some kind of errors, too (dependency ones, for example).