On 15 avril 21:53, Mikko Ohtamaa wrote: > Hi all, Hi, > I am working on a generic linting and validation continuous integration too > where pylint is one validator: > > https://github.com/miohtama/vvv > > Since pylint seems to be little slow when run against the whole project I > was hoping to ask what kind options there exist to speed-up pylinting > > - What is the best way to run pylint on small subset of files?
I'm not sure about what do you expect here. The pb is that even on a small subset, pylint will usually have to gather information from a lot of other files to get inference working. "pylint -E" speed up things by disabling part of analysis, though there is still ongoing work on this to avoid doing some stuff when some messages are disabled. Another potential optimisation would be to cache some intermediary results of the inference work. But I won't go in deeper details without knowing if that's the kind of stuff you're asking for... > - Would there be any gains using PyPy instead of CPython? Does pylint > re-cycle some internal parts of Python and is this even possible? pylint, or more precisely astng, build its syntax tree from python's ast module. I've never tried to run pylint using pypy, but would be greatly interested by the results. -- Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (09.54.03.55.76) 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 _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
