false-positive abstract-class-not-used when implementations are not in same file

[pylint-bot]

Originally reported by: Bengt Lüers (BitBucket: Bengt, GitHub: @Bengt?)

---

I have configured PyDev to use PyLint on my project, but it does not find implementations if they are in different files than their abstract base classes (module abc in the standard library). However, if I run pylint src, it will not complain about missing implementations. Should PyLint perhaps be called on the project folder by PyDev instead of being called on individual files, since PyLint considers them to be self-contained?

See https://sw-brainwy.rhcloud.com/tracker/PyDev/219

---

• Bitbucket: https://bitbucket.org/logilab/pylint/issue/101

[pylint-bot]

Original comment by Sylvain Thénault (BitBucket: sthenault, GitHub: @sthenault?):

---

this sounds like a pydev related pb, hard to do something on the pylint side.

[pylint-bot]

Original comment by Bengt Lüers (BitBucket: Bengt, GitHub: @Bengt?):

---

I composed a gist that demonstrates the problematic behavior. As one can see, PyLint detects the using class correctly, when run on both files at once.

When encountering this error, one can suspect that it might get resolved by looking at more files at once. So the correct reaction would be to run PyLint at the next parent directory, up to the root of the project. Since PyLint has no way of knowing where the project root is and running on / would be very slow, I think this should get handled by PyDev, which knows the project root and can stop at that. Additionally, Eclipse's related projects could get added when the usage is still not resolved at the project root.