-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
inconsistent-mro , but Python does not raise error #1377
Comments
It might be a false positive. We are trying to compute the MRO, but we might have some edge cases we didn't handle properly when we first implemented the algorithm. Thank you, will take a look. |
There is a magic decorator in twisted source that converts old-style class to new-style classes in runtime. Most likely Pylint still sees this class as old-style class, which changes the way MRO works. Our C3 algorithm implementation looks fine to be honest. |
Slightly smaller, standalone reproduction. |
Closed in astroid's master by pylint-dev/astroid@5092504 |
Steps to reproduce
pip install autobahn[twisted]
Current behavior
Expected behavior
Too many ancestors is expected, given the library imports at hand.
However, we can't reproduce the inconsistent method resolution order on a Python execution of the script. Isn't this a false positive?
pylint --version output
The text was updated successfully, but these errors were encountered: