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
Fix crash in super-init-not-called
checker
#6043
Conversation
Pull Request Test Coverage Report for Build 2069291873
💛 - Coveralls |
Uhm.. Does |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we need to forbid the use of infer accross all the pylint codebase, there's no way we're not going to get a crash eventuellay with the diversity of code pylint is going to be run on.
We might need to do
What do you think @DanielNoord ? |
I mean we could, but I don't know why this doesn't work on PyPy. I don't know the |
Looks like the PyPy behavior is correct -- super's init is not being called, so the test file should have a |
I guess raising if we can't infer will lead to more issues right? |
Yes I think we should prefer a false negative always when we're not sure. |
Co-authored-by: Jacob Walls <jacobtylerwalls@gmail.com>
Co-authored-by: Pierre Sassoulas <pierre.sassoulas@gmail.com> Co-authored-by: Jacob Walls <jacobtylerwalls@gmail.com>
doc/whatsnew/<current release.rst>
.Type of Changes
Description
Closes #6027.
Should have never put that comment there...