-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Astroid 2.0.1 Regression: Metaclass call no longer understood. #2335
Comments
Hi @kayhayen Thanks for the report! Can you also add in the description how the call site looks like for that error you are getting? It seems it involves the |
I am not sure what you mean, with call site, I am not calling "new" myself. I do something unusual with the metaclass afterwards:
|
Yes, that's what I was interested in, thanks. |
I get a similar error when subclassing this class: With this example:
I get this error:
The error makes no sense to me, on that line I pass This is with astroid and pylint master from today.
If it's useful for you to have this in a separate issue, let me know and I'll copy this comment there. |
Thanks @cdeil ! Let's move this to a separate issue, it seems related but a bit different at the same time that it should be on its own. |
OK, I've opened #2441 . |
Steps to reproduce
Current behavior
Warning is given:
nuitka/nodes/NodeMetaClasses.py:66 E1121 too-many-function-args
NodeCheckMetaClass.new Too many positional arguments for
classmethod call
Expected behavior
I would be really surprised if that new call got too many arguments for real. I expect no warning to be given of course. Maybe it has to do with bad-mcs-classmethod-argument which seemed to no longer be an issue with 2.0.0, which I currently do not use due to lack of Python3 support for 2.0.1
pylint --version output
python3.6 -m pylint --version
main.py 2.0.0
astroid 2.0.1
Python 3.6.3 (default, Mar 27 2018, 00:29:24)
[GCC 6.3.0 20170516]
The text was updated successfully, but these errors were encountered: