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
new unused-private-member causes a crash #4755
Comments
stanislavlevin
added
Bug 🪲
Needs triage 📥
Just created, needs acknowledgment, triage, and proper labelling
labels
Jul 27, 2021
traceback for today's
|
IMO, non-current node's private attributes should be skipped. |
Pierre-Sassoulas
added
Crash 💥
A bug that makes pylint crash
and removed
Needs triage 📥
Just created, needs acknowledgment, triage, and proper labelling
labels
Jul 27, 2021
hi, looked into it and came up with a PR :) please take a look |
The fix is verified. Thank you! (fixed + no regressions were found) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
Given a file
test.py
:(Configuration)
No response
Command used
Result of
pylint test.py
:(Expected behavior)
pylint shouldn't crash.
(Version affected)
pylint 2.9.0+ (including today's main).
(OS / Environment)
ALTLinux
(Additional dependencies)
No response
The text was updated successfully, but these errors were encountered: