I'm having problems using the PyLint integration. PyLint is correctly installed, working and producing correct warning when run from command line. I've followed the instructions and enabled PyLint from the preferences menu and specified the file path. However nothing specials appears in the console or problems tab when I run my script.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When you save your file, if that file is under a source folder, that file should be analyzed (provided you have the auto-build turned on -- more details at http://pydev.sourceforge.net/pylint.html )
Cheers,
Fabio
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Here's a naive question. What does Pylint add beyond what Pydev seems to do in terms of detecting errors etc. There is some amount of this built in it seems like in my experience. Thanks,
Lin
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
PyLint does things similar to the Pydev Extensions code-analysis plus some checks on the coding style (i.e.: following pep 8) -- although it's significantly slower than Pydev Extensions for the code analysis bits.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Pylint takes care of stuff like enforcing conventions (variable names, function names, etc.), checking for uninitialized variables, give out warnings for undetected variables, give some refactoring advice (too many local variables, too many parameters), check whether the called methods of an object exist.
I'm not sure how many of the above items are directly built into pydev, I suppose it mainly detects simple syntax errors.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-02-08
I'm having the same issue… Eclipse 3.5.1, Pydev 1.5.4.2010011921
I couldn't figure out why this helped (because the .pydevproject remained the same), but I created a new project and re-imported the old source, that worked.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm having problems using the PyLint integration. PyLint is correctly installed, working and producing correct warning when run from command line. I've followed the instructions and enabled PyLint from the preferences menu and specified the file path. However nothing specials appears in the console or problems tab when I run my script.
OK, it works. Apparently I had to put my files under a src folder
What does that mean? I'm having the same problem but I don't know what a 'src' folder is.
Is there not some way to tell pylint to operate on the file that I'm currently editing?
A 'src' folder is a folder that's specified as being in your project pythonpath (see http://fabioz.com/pydev/manual_101_project_conf2.html for details on that).
When you save your file, if that file is under a source folder, that file should be analyzed (provided you have the auto-build turned on -- more details at http://pydev.sourceforge.net/pylint.html )
Cheers,
Fabio
That made a big difference. Thanks.
Here's a naive question. What does Pylint add beyond what Pydev seems to do in terms of detecting errors etc. There is some amount of this built in it seems like in my experience. Thanks,
Lin
Pydev only has syntax checking.
Pydev Extensions has code analysis. See: http://fabioz.com/pydev/manual_adv_code_analysis.html
PyLint does things similar to the Pydev Extensions code-analysis plus some checks on the coding style (i.e.: following pep 8) -- although it's significantly slower than Pydev Extensions for the code analysis bits.
Pylint takes care of stuff like enforcing conventions (variable names, function names, etc.), checking for uninitialized variables, give out warnings for undetected variables, give some refactoring advice (too many local variables, too many parameters), check whether the called methods of an object exist.
I'm not sure how many of the above items are directly built into pydev, I suppose it mainly detects simple syntax errors.
I'm having the same issue… Eclipse 3.5.1, Pydev 1.5.4.2010011921
I couldn't figure out why this helped (because the .pydevproject remained the same), but I created a new project and re-imported the old source, that worked.