[Python-projects] pyLint: Speeding up pyLint
Sylvain Thénault
sylvain.thenault at logilab.fr
Tue Jun 2 18:29:57 CEST 2009
On 29 mai 23:11, Julian Scheid wrote:
> I've also patched pylint today to use the multiprocessing module in
> order to parallelize the checker runs. That turned out to be trivial
> and while it doesn't provide a linear speed-up (as is to be expected),
> it does improve performance significantly on multicore machines. I'll
> tidy up the code and send over a patch soon.
great
> Here's another idea that occurred to me. If checkers could be
> categorized into those that only work locally on a single file (e.g.
> check number of statements per function) and those that need
> information from other files (e.g. method not overridden) then for
> files that haven't changed between pylint runs (usually the majority
> of files) only the latter would have to be run. Unfortunately, from a
> quick look at the checkers it looks like local/global checks are often
> intermingled in the same source file. Still, this could be one
> approach to pursue. Thoughts?
today, checkers regroup checks more or less semantically (at least try to).
If another organisation could leads to some consequent speed-up, it's ok with
me.
> Thanks again for these pointers. I am acquainted with CI but I wasn't
> aware of Hudson and the pylint integration via the Violations plug-in
> yet. I'm playing with it at the moment and it works very well. I'll
> check out apycot next week.
IMO, apycot is not yet ready for prime time, mainly because it's too hard
to configure and get it running. I hope to work on this in a near future,
stay tunned on this list for announce ;)
--
Sylvain Thénault LOGILAB, Paris (France)
Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations
Développement logiciel sur mesure: http://www.logilab.fr/services
CubicWeb, the semantic web framework: http://www.cubicweb.org
More information about the Python-Projects
mailing list