Open maciejmatuszak opened 2 years ago
Thanks for the report. As I understand it, you're reporting these inconsistencies:
_single_leading_underscore
when the first letter has the wrong case given a setting for camelCase, PascalCase, etc.__double_leading_underscore
, which is OK as a PEP8 "name mangling" name for class attributesThese could probably be solved separately.
Bug description
I am trying to use
<>-naming-style=<>
syntax in pylintrc file, however there seems to be couple problems around "private" and "protected" class/instance members. According to PEP8 leading underscore(s) are special case most commonly described as protected and private members:From the behaviour exhibited by pylint it looks it threat the leading underscore as lower case letter instead of "access modifier" as intended by PEP8. The config supplied is default generated by pylint with some
<>-naming-styles
styles modified and disabled irrelevant warnings. See the lines I marked asERROR:
belowConfiguration
Command used
Pylint output
Expected behavior
see above code marked with
ERROR:
Pylint version
OS / Environment
Ubuntu 20.04
Additional dependencies
none