-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Allow certain short argument/variable names that make perfect sense #2709
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Please check the good-names option, which does exactly this. |
And what about function/method names? A function with a 2-letter name gives an warning. I don't see a |
@gitaarik You are probably interested in configuring |
Sorry, the |
Is your feature request related to a problem? Please describe
pylint complains about variable/argument names like
x
,y
.Describe the solution you'd like
Whitelist variable names that are typically OK despite being really short
Additional context
See https://github.com/mkenyon/rubocop/blob/master/config/default.yml#L792 for how Rubocop (linter for Ruby) solves it for their UncommunicativeMethodParamName equivalent
See #2018 for a related problem where short names are misleadingly described as not being snake_case
The text was updated successfully, but these errors were encountered: