Thread: [Pydev-code] pylint problems
Brought to you by:
fabioz
From: Heikki T. <hj...@co...> - 2006-04-28 05:19:58
|
I noticed I haven't had pylint report me problems lately, but I don't know when this broke. I did notice the report in the console (when I had enabled pylint messages in console). Today I upgraded to latest pylint (0.11.0), and now there isn't even anything in the console. I know some warning codes have been removed and I tested my options on the command line until I found a list that I know works. However, nothing seems to happen when running with pydev. Anybody else experienced this? Any ideas? -- Heikki Toivonen |
From: Fabio Z. <fa...@gm...> - 2006-04-28 10:31:20
|
Well, in latest versions you can have pylint show you its console (configur= e in the pydev preferences). Do you see something there? On 4/28/06, Heikki Toivonen <hj...@co...> wrote: > > I noticed I haven't had pylint report me problems lately, but I don't > know when this broke. I did notice the report in the console (when I had > enabled pylint messages in console). > > Today I upgraded to latest pylint (0.11.0), and now there isn't even > anything in the console. I know some warning codes have been removed and > I tested my options on the command line until I found a list that I know > works. However, nothing seems to happen when running with pydev. > > Anybody else experienced this? Any ideas? > > -- > Heikki Toivonen > > > ------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim= o > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > _______________________________________________ > pydev-code mailing list > pyd...@li... > https://lists.sourceforge.net/lists/listinfo/pydev-code > |
From: Heikki T. <hj...@co...> - 2006-04-28 15:44:47
|
Fabio Zadrozny wrote: > Well, in latest versions you can have pylint show you its console > (configure in the pydev preferences). Do you see something there? I did mention that I tried it in my original message. After the pylint upgrade there is nothing in the console. > On 4/28/06, *Heikki Toivonen* <hj...@co... > <mailto:hj...@co...>> wrote: > > I noticed I haven't had pylint report me problems lately, but I don't > know when this broke. I did notice the report in the console (when I had > enabled pylint messages in console). > > Today I upgraded to latest pylint (0.11.0), and now there isn't even > anything in the console. I know some warning codes have been removed > and > I tested my options on the command line until I found a list that I know > works. However, nothing seems to happen when running with pydev. > > Anybody else experienced this? Any ideas? -- Heikki Toivonen |
From: Fabio Z. <fa...@gm...> - 2006-04-28 15:48:03
|
On 4/28/06, Heikki Toivonen <hj...@co...> wrote: > > Fabio Zadrozny wrote: > > Well, in latest versions you can have pylint show you its console > > (configure in the pydev preferences). Do you see something there? > > I did mention that I tried it in my original message. After the pylint > upgrade there is nothing in the console. Did you try to run it from the command-line? Also, did you check to see if the lint.py location is correct in the preferences? |
From: Heikki T. <hj...@co...> - 2006-04-28 20:44:53
|
Fabio Zadrozny wrote: > Did you try to run it from the command-line? Also, did you check to see > if the lint.py location is correct in the preferences? Heh, are you reading my messages at all: I said I confirmed it worked on the command line in the first message, which was also quoted in the second message. But I did spend some more time looking at settings and trying different things... The lint.py location is correct. I have checked FATAL, ERRORS, WARNINGS in the checkboxes. Currently the options manually specified are: --persistent=n --comment=n Builders are enabled, build on save only not checked (this does not make a difference, tested). The problems view filter is set to show stuff for currently selected only, all types enabled, severity not checked (this does not seem to make a difference, tested). After more tests, it seems some kinds of errors do get reported at least part of the time, although there is still nothing in the console. Some types of errors that are reported: - bad indentation - somevar = Some types of errors that are not reported: - unused imports -- Heikki Toivonen |
From: Fabio Z. <fa...@gm...> - 2006-04-28 23:00:57
|
> > Builders are enabled, build on save only not checked (this does not make > a difference, tested). > Ok, I just got the latest Pylint version myself and it works for me... Actually, when you mentioned the builders, this reminded me of something: are your files in the project pythonpath? In previous versions it would try to analyze all your files, even if your pythonpath was not correctly defined, so, there's a chance that your files are not underneath a source folder in the project. -- you have to define the source folders for that... check http://fabioz.com/pydev/manual_101_project_conf2.html (and the auto-build should also be set -- http://pydev.sourceforge.net/pylint.html discusses that). Cheers, Fabio |