Closed junaruga closed 7 years ago
I don't think it adds readability much. Actually I think it makes the code less readable.
I don't think it adds readability much. Actually I think it makes the code less readable.
Agreed. If we really want this kind of checking, we need a way to mark an argument as "deliberately unused" (i. e. part of the API callback). AFAIK pylint
does not provide something like that out of the box, so we would need to come with our own documented convention.
I agree with you, guys.
There are several cases for the warnings in current source code.
Which case is better to use underscore variable?
I want to investigate those cases more when I have a time. For example, what is a better practice to use a type hints and a kwargs together? (Case 3) So, I want to keep this ticket right now.
__init__
: Related to get_instanceprepare_extra_steps
: Related to child class's structure.work.each_num_dir
's return values.
I ran
pylint
to know Python better practices in my repository (https://github.com/junaruga/rpm-list-builder/tree/feature/add-pylint) as a trial.And I fixed below unused-argument and unused-variable warnings. How do you think?