-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
find_pylintrc
removed in 3.0
#9105
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
@Pierre-Sassoulas Do you think it could be related to your recent 3.0.0 release? |
Hi @Alexander-Serov 👋 The release notes are a bit long, but it's in there 😉 :
Duplicate of #8862 |
Thanks for identifying it fast. So just to be sure I understood the discussion in the other thread correctly: the .pylintrc has been deprecated and one should migrate the config to |
I'm sympathetic to the fact this this is a little hard to parse out of the release notes. I guess in your case the specific news fragment is this one:
But even more visible than the release note would have been the deprecation notice. |
Ah, no! rc files are still fine. You can provide an exact path or rely on the discovery in the order given here. Hope that helps. |
find_pylintrc
removed in 3.0
Thanks, @jacobtylerwalls, it does. |
cc/ @DanielNoord for future, it's occurring to me now that pre-commit hooks probably swallow deprecation warnings. Not sure what to make of that, just hadn't thought of that before. |
Yeah, makes sense. The amount of plugin related issues also seems to confirm this.. Good call on changing the name, let's hope people find these issues before opening new ones. |
This is a byproduct of the approach for setting the sys/PYTHONPATH recommended here: https://stackoverflow.com/questions/1899436/pylint-unable-to-import-error-how-to-set-pythonpath. A "best practices" approach for this problem should probably be highly visible somewhere here in this Github repo. |
Bug description
Downgrading to pylint==2.17 solves the problem.
Pylint output
Expected behavior
Same behavior as in 2.17
Pylint version
OS / Environment
Linux / Macos
Additional dependencies
No response
The text was updated successfully, but these errors were encountered: