-
Notifications
You must be signed in to change notification settings - Fork 48
PYTHONPATH hacks break inner pylint imports #104
Comments
this has tortured me today, thank you @cblp; i'm new to atom and without this hint - i was looking into wrong places basically, when linter-pylint exports PYTHONPATH; it can break the python! i believe the right solution IFF you want to export PYTHONPATH (and only if it is not set already): is to mege the user setting with the default path, ie:
and append the user setting to this value |
Basically the error here is that +1 for a better default |
I also ran into this same problem because I have a file named Proposing this change:
And put a warning on the setting that %f and %p may cause pylint to trigger errors if any modules shadows standard library file names. |
I am also experiencing this problem. I have a package named |
I am also having the same issues right now. The And removing |
linter-pylint messes with PYTHON_PATH in ways that cannot be configured out. That is WRONG. The immediate problem I am encountering is linting files in a package that contains a "importlib" module. It conflicts with the global importlib, which prevent pylint from running. It might be poor style but it must not prevent the linter from running! You need to add projectDir or fileDir? Use the existing pythonPath configuration system. Do not make the current broken behaviour into a default that is going to waste the time of thousand of people in the future. Just fix it. I am making a PR right now. |
PR #213 |
To reproduce: jsut create and open empty file
types.py
:Pylint tries to import system module
types
, but local filetypes.py
steps in.The text was updated successfully, but these errors were encountered: