PyLint in PyDev only analysing files in top-most project directory

Question

My project directory is something like

src
    ProjectName
        Package1
            __init__.py
            Module1.py
            Module2.py
        Package2
            __init__.py
            Module3.py
            Moduel4.py
        __init__.py
        main.py
        setup.py

When I do Project->Clean..., PyLint runs, but only on the three files in the uppermost package: __init__.py, main.py, and setup.py.

I have gone into Project->Properties->PyDev - PYTHONPATH, and all of the source folders are definitely listed there, so I'm not sure why most of them aren't being analysed.

Also, like this question, PyDev doesn't seem to be parsing the PyLint output, as the errors and warnings that show up in the console aren't in the 'Problems' output tab, or in the editor margins. This makes me think it might be a version/regression problem, as it was for that question. I might try an older version of PyLint and see if that works.

I'm using Eclipse Helios, PyDev 2.2.1, PyLint 0.25.1, and Python 2.7.

score 3 · Accepted Answer · answered Jan 24 '12 at 14:07

3

The PyLint configuration (window > preferences > pydev > pylint), has a 'maximum number of processes for PyLint', so, it'll only run analysis on 'n' files simultaneously (because spawning too many processes at once could bring your machine to a halt).

So, you can raise that number for the analysis and and it should analyze more files at once (I'd recommend raising it for that analysis and then reducing the number again, as you don't usually want too many processes running at once).

As for the output, it could be that PyLint changed its format (please report that as a bug in the pydev sourceforge tracker if you believe that's the case).

answered Jan 24 '12 at 14:07

Fabio Zadrozny

24,814
4
66
78

Increasing the number of processes fixed the files problem. The PyLint website is down for maintenance at the moment, so I'll have to try downgrading once it's back up. – Cam Jackson Jan 30 '12 at 00:01
Turns out I didn't need to downgrade PyLint, I needed to update PyDev. I had Eclipse's update detection turned off, so I didn't realise there was a new version out. No problems with PyDev 2.3 and PyLint 0.25.1. – Cam Jackson Jan 30 '12 at 23:02

score 2 · Answer 2 · answered Jan 24 '12 at 08:56

2

This could be caused by recent changes in Pylint's output format which now prints column offset. You should contact the pydev maintainers reporting this.

answered Jan 24 '12 at 08:56

gurney alex

13,247
4
43
57

score 1 · Answer 3 · answered Mar 12 '15 at 16:08

I just discovered that if the file you are trying to lint is not a valid python module name, then pylint will (silently) not run on it. For example if you have an executable python script named do-thing, in your projects bin directory, it will simply not be linted. Rename the file dothing and suddenly it will work (no .py) extension is needed.

score 1 · Answer 4 · edited May 23 '17 at 11:52

I have gone into Project->Properties->PyDev - PYTHONPATH, and all of the source folders are definitely listed there.

If you mean you have there subfolders from your project (Package1 and Package2) then it's not necessary. You should have only your project's main folder there.

I use PyDev 2.3.0 and when cleaning a project all project's files are being processed by Pylint. Problem with parsing Pylint's output was fixed in PyDev 2.2.2 See my answer here.

PyLint in PyDev only analysing files in top-most project directory

4 Answers4