I'm using the pylint python linter via Syntastic in Vim. It's great, except that I'm getting a lot of undefine-variable messages when calling functions that are defined in other modules that are then imported. Is it possible to configure Syntastic so that pylint looks in all files reachable from my current directory?
Asked
Active
Viewed 68 times
2
Tom
- 6,601
- 12
- 40
- 48
-
1Is your working directory of vim correctly at the root of your project and are other files readable from there through proper packages with `__init__.py` files? – languitar Sep 16 '16 at 14:30
-
Yes, with empty __init__.py files – Tom Sep 16 '16 at 15:07
-
1And this also happens if you run pylint manually on the file? – languitar Sep 16 '16 at 15:13
-
Yes, it does indeed – Tom Sep 16 '16 at 15:23
-
Can you make `pylint` not complain about undefined variables when running it from the command line? – lcd047 Sep 17 '16 at 05:00
-
I just tested this with a dummy example without any problems. In order to solve this we need a minimal working example and the exact pylint version. – languitar Sep 19 '16 at 07:42