On Sun, Dec 21, 2014 at 7:16 PM, Chris Martin <ch.mar...@gmail.com> wrote: > Pylint runs for several minutes on my project; I'd like to add it to my CI > build, but I'm not sure I want to introduce that much delay. > > Is there any trick to optimizing it? Are there some particularly slow > inspections that I could disable?
I'll let others identify slower checks. I've never found pylint to be a big deal performance-wise, especially when compared to traditional compiled systems. (Perhaps you've never built large C++ systems?) Here are my thoughts: * If you find it useful, why disable something just because it's a bit slow? Would you prefer to miss possible problems in favor of running a bit faster? * Couldn't you just run pylint on the subset of files which have changed? * Are you running one massive pylint across all modules in your system? Perhaps break it into multiple runs on (possibly overlapping) subsets of the system which would either run faster one-by-one, or could be run in parallel. * Doesn't this stuff run off on its own while you're busy doing other things? Is it really holding you up, or is it just perception? My 2ยข... Skip _______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
