I'm using Eclipse Helios build id 20110218-0911 and PyDev 126.96.36.1991071313 on Mac OS X 10.7. First, I should mention that everything was working fine before I upgraded to OS X Lion. After doing that, things were very broken, but I was able to fix most problems by reconfiguring PyDev (updating the library paths) and reinstalling PyLint using easy_install. Everything seems to be working now except for one thing. When I save a file or do a project clean, PyLint runs successfully and shows the output in Console, but none of the issues it finds are shown in the Problems tab. Any idea how to fix this?
Not sure what may be happening… Do you have some error in your error log? Are your files under a source folder? Maybe you have some filter that's hiding those issues?
At the bottom of the PyLint output, there is "PyLint: The stderr of the command line is: No config file found, using default configuration", but I don't see anything else.
Ok, I do have errors in my error log. I'm not too familiar with Eclipse so I didn't know exactly what you were referring to. They all look like this:
For input string: "9,0"
Exception stack trace:
java.lang.NumberFormatException: For input string: "9,0"
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64
There's one for every line pylint finds an issue on, it seems. Also, though I said in my original post that I was on Mac OS X, I migrated my workspace to my Linux machine, hence the session data, but am getting the same problems.
Can you create a bug report and add the output that pylint is giving you when you run it?
Also, please add information on the pylint version you're using.
I guess you have the latest PyLint version 0.24.0 and problem you see has been already reported by me in the issue 3376410 java.lang.NumberFormatException with PyLint 0.24.0 and by Barbara in the issue 3386299 pylint NumberFormatException
Just fixed. Please grab the nightly build in a couple of hours to see if it works for you.
Verified using PyDev 188.8.131.521081814 and PyLint 0.24.0 - bug is fixed.
Yes, bug is fixed! Thank you.