You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pep8-naming does not allow functions starting or ending with a dunder (__). This is not something that is disallowed by PEP8 and I think this rule should be removed. However if this check remains then it should be moved to it's own check and should not be part of the more general "functions should be lowercase" check so that people can disable it in their own projects without disabling the useful lowercase function check.
The text was updated successfully, but these errors were encountered:
Dunder functions really shouldn't be marked in this check.
I do believe a separate check for this is useful because, by themselves, dunder functions have absolutely no different meaning from functions with a single underscore and thus are redundand.
Since PEP-8 doesn't have a stance regarding those, the check should probably be disabled by default?
jparise
added a commit
to jparise/pep8-naming
that referenced
this issue
Jan 8, 2018
This check appears controversial (PyCQA#9) because PEP8 doesn't mention this
as an official naming rule. This change moves it to its own error code
so that it can be disabled separately.
pep8-naming does not allow functions starting or ending with a dunder (
__
). This is not something that is disallowed by PEP8 and I think this rule should be removed. However if this check remains then it should be moved to it's own check and should not be part of the more general "functions should be lowercase" check so that people can disable it in their own projects without disabling the useful lowercase function check.The text was updated successfully, but these errors were encountered: