This project has moved. For the latest updates, please go here.
1

Resolved

PyLint fails if working directory is not the project root

description

PyLint is run under the project's General -> Application -> Working Directory, which means it outputs this for every file:

xxxx.py(1,0): warning F0001: No module named xxxx.py

I would expect it to ignore this parameter and always run under the project file's directory.

Workaround:

Set Working Directory to '.' whenever you need to run PyLint.

comments

Zooba wrote Jan 17, 2015 at 3:33 PM

Good catch! We should be able to make a simple fix for this. When we do (if it's as easy as I think) we'll be able to post it here so you won't need the workaround.

ViM3 wrote Aug 19, 2016 at 12:26 PM

I got this problem in OSX .
pylint work when opening a file ..
code foo.py
but fails when project in a directory
code .