28

Resolved

pylint support/integration

description

Either a 'build' task (project option) or a menu item to run pylint on the current package/project.

Perhaps a "Suppress Message" context menu for warnings.

pylint can be slow, so running it constantly is probably a bad idea (though once it's loaded into the slave Python process it may be okay).

comments

Zooba wrote May 4, 2011 at 11:32 PM

For the record, I'd prioritise unit testing integration over pylint integration, though both would be nice.

hitamar wrote Apr 15, 2012 at 8:22 PM

I actually think this would be terrific. It saves tons of time in pydev (the eclipse environment). Regarding it being slow, it is not too bad (only run it on the currently active file of course)

Zooba wrote Feb 18, 2013 at 8:34 PM

Also need to warn when we can't find a requested import.

pminaev wrote Jan 20 at 8:48 PM

This is coming in 2.1 alpha.