-
-
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
protected-access and @classmethod cls #1159
Comments
I'm using Landscape.io, which uses pylint to check my Python code. I reported there another example for a falsely reported access to a protected member. See Landscape falsely reports an access to protected members for more details. Note my presented example uses type hints, which are not evaluated by pylint as it seems. |
I get this error with pylint version 2.5.3 on Python 3.8.0, is this in the pipeline of getting fixed? |
@mkielg11 can you give us a snippet of your issue please? |
Well, yes, sorry @hippo91 for long reply time. The example is, however, exactly as above:
Result:
|
@mkielg11 thanks for your snippet. I can reproduce it. Unfortunately nobody has been interested in fixing this bug. |
You mean that I could propose a fix? I guess I may be able to, however, I have no insight in the pylint source code, so I think I'll pass on that. |
This is one bug that irks me enough I'd like to have a crack at solving it. I haven't worked with the codebase before, though, so I'm not sure where to start. Is there a getting-started guide or something similar that would help me in figuring out where to start fixing this? |
Sure thing @irgeek thank you for willing to contribute, I assigned you to the issue. You can find the developper doc here: http://pylint.pycqa.org/en/latest/development_guide/contribute.html |
Steps to reproduce
Current behavior
W: 7,10: Access to a protected member _Foo of a client class (protected-access)
Expected behavior
Seems like this should be allowed, for consistency with regular methods
pylint --version output
The text was updated successfully, but these errors were encountered: