New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pylint 2.7.2 can't find its plugins on PYTHONPATH if the latter points to cwd #4252
Comments
Hi @stanislavlevin, |
@sbraz, neither absolute nor relative path work. I pointed to concrete commit with which the issue happens. |
This worked for years. In particular, the regression breaks FreeIPA (https://github.com/freeipa/freeipa/blob/master/Makefile.am#L363). |
Shrug, I just wanted to fix some failing tests, maybe the commit should just be reverted. |
This is not distro-friendly(script name differs from distro to distro). Revert this back after fixing: pylint-dev/pylint#4252 Signed-off-by: Stanislav Levin <slev@altlinux.org>
This is not distro-friendly(script name differs from distro to distro). Revert this back after fixing: pylint-dev/pylint#4252 Signed-off-by: Stanislav Levin <slev@altlinux.org>
This is not distro-friendly(script name differs from distro to distro). Revert this back after fixing: pylint-dev/pylint#4252 Signed-off-by: Stanislav Levin <slev@altlinux.org>
@Pierre-Sassoulas Do you have a suggestion how we should handle this one? Should we revert the change? If so, it might make sense to include it in |
We'll need to add tests again, but I don't know how to fix precisely. Those change were done to handle python path starting or ending with a colon, so I think not being able to use our plugins is a bigger problem than not handling python starting or ending with a colon. I think the fast thing to do would be to revert and add something in the doc about the current pythonpath limitation, what do you think ? |
I might have found a way to fix this one without reverting the previous change: #4258 |
The fix was verified. Thank you! |
Steps to reproduce
Current behavior
Pylint can't find plugins in current working directory(PYTHONPATH is set to this directory):
The regression is caused by cc8d918:
Changing the cwd can workaround this.
In the meantime:
predictable doesn't cause such behaviour.
Expected behavior
Pylint should find its plugins in PYTHONPATH.
pylint --version output
Result of
pylint --version
output:Also checked on master(same result).
The text was updated successfully, but these errors were encountered: