[Python-projects] pyLint: Speeding up pyLint

[Alexandre Fayolle]

On Friday 29 May 2009 11:31:32 Nicolas Chauvat wrote:
> > 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).
>
> I agree with Jurgen that continuous testing is a good option.

I've been using Eclipse with Pydev + pylint while working on-site and the 
integration is great : you can easily see which files have been diagnosed 
with  Errors / Warnings with the Problems view, and when editing a file, you 
get quick access to the incriminated lines via tags in the margin of the 
editor (and lots of things are configurable of course). 

epylint can be used with emacs + flymake mode, but it is not quite as nice -- 
although it gives some quick and continuous feedback.

-- 
Alexandre Fayolle                              LOGILAB, Paris (France)
Formations Python, Zope, Plone, Debian:  http://www.logilab.fr/formations
Développement logiciel sur mesure:       http://www.logilab.fr/services
Informatique scientifique:               http://www.logilab.fr/science