Question

I have pylint installed (works fine on the command line) and set up within Pydev in Eclipse.

Pylint is being triggered OK when I edit files, and is outputting to the Eclipse console.

But, the pylint warnings don’t appear as marks in the editor margin (in the same way as compiler warnings and errors)

Newly-generated warnings don’t appear in the Problems view either – there are some old ones showing, but they disappear if I re-save the relevant module.

I know this is possible as I’ve had it working previously – but how do I set this up?

Ticking or unticking “Redirect Pylint output to console?” doesn’t seem to make any difference.

Answer 1

I had this exact problem today, on a brand new system. I tracked down the cause, and it seems that PyDev refuses to pick up the messages from pylint 0.24.0, which was released on July 20, 2011.

Reverting to the previous version (pylint 0.23.0) seems to have solved the problem. For me, that involved removing everything from Python’s Lib/site-packages directory that was related to pylint, and then running python setup.py install from the directory I’d extracted pylint 0.23.0 into. (Without deleting those files in the site-packages directory first, it kept using the new version.) But after both those steps, the messages started showing up in PyDev as expected.

You can check your pylint version with pylint --version from a shell prompt; if it shows 0.23.0 you’re good to go.