Pylint does not show warnings in Problems tab
Brought to you by:
fabioz
Menu
▾
▴
I am having issues get pylint to run either when saving a file or when I build the project. I have pylint installed and it runs fine when I call it from the command line. I am running Eclipse 3.5.2, PyDev 1.5.7.2010050621, and Ubuntu 10.04. Both Eclipse and pylint were installed using Ubuntu's package manager. I have gone to Window->Preferences->PyDev->Pylint and checked use pylint and even created a symbolic link so that lint.py was under site-packages as some places have suggested. The exact location is /usr/local/lib/python2.6/site-packages/pylint/lint.py. The original location of the file is /usr/lib/pymodules/python2.6/pylint/lint.py. If I go to configure contents on the Problems tab of Eclipse, I check all the configurations ("All Errors", "Warnings on Selection", etc.). Under types, PyLint Problem is checked. When I have a standard python error, this will appear under problems, but not any pylint warnings. If I run pylint from the command line, there are clearly issues with the file. I have tried looking on the documentation on pydev.org, but it appears that it is out-dated and attempting to following it as well as possible has not worked. Does any one have any suggestions? Thanks!
I have to confirm this issue on my Mac OSX with pylint from Mac Ports at: /opt/local/bin/pylint.
This is a small script using: /opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/pylint/lint.py
Installed from py26-lint package.
In my case pylint runs fine from command lin. In Eclipse, when I redirect output from pylint to console it also works fine. It's just the messages don't show up in the 'Problems View'. Just like the original poster I have ensured the right items are configured there (I hope).
I'm running the latest pydev version 2.2.0.xxxx. Eclipse 3.5 and:
pylint 0.23.0,
astng 0.21.1, common 0.55.1
Python 2.6.6 (r266:84292, Jun 17 2011, 16:46:33)
I have also tried pydev version 2.0 instead of 2.2 to no avail.
Important question for debugging this: Does the checkbox 'Redirect pylint output to console?' also prevent it from ending up in the Problems Tab? I don't think so but…
A couple of screenshots hopefully show more.
Thanks guys!
Hi again, my previous message (@2011-06-28 16:18:46 CEST) can be ignored. I found out that pylint was picking up an old rcfile (in my ~/.pylintrc) by default.
In there I misconfigured
output-format=parseable
when changed back to the original:
output-format=text
the integration with eclipse/pydev worked fine again.
Sorry to have bothered anybody.