When \"deconstructing\" a tuple, I can use _
to denote tuple elements I\'m not interested in, e.g.
>>> a,_,_ = (1,2,3)
>>> a
1
A funny way I just thought of is to delete the variable:
def f(foo, unused1, unused2, unused3):
del unused1, unused2, unused3
return foo
This has numerous advantages:
del
is the solution recommended in the PyLint manual.If you have both args and keyword arg you should use
def f(a, *args, **kwargs):
return a
The underscore is used for things we don't care about and the * in *args denotes a list of arguments. Therefore, we can use *_ to denote a list of things we don't care about:
def foo(bar, *_):
return bar
It even passes PyCharm's checks.
You can use '_' as prefix, so that pylint will ignore these parameters:
def f(a, _b, _c):
I think the accepted answer is bad, but it can still work, if you use what I should call "Perl way" of dealing with arguments (I don't know Perl really, but I quit trying to learn it after seeing the sub
syntax, with manual argument unpacking):
Your function has 3 arguments - this is what it gets called with (Duck typing, remember?). So you get:
def funfun(a, b, c):
return b * 2
2 unused parameters. But now, enter improved larsmans' approach:
def funfun(*args):
return args[1] * 2
And there go the warnings...
However, I still enjoy more the boxed's way:
def funfun(a, b, c):
del a, c
return b * 2
It keeps the self-documenting quality of parameter names. They're a feature, not a bug.
But, the language itself doesn't force you there - you could also go the other way around, and just let all your function have the signature (*args, **kwargs)
, and do the argument parsing manually every time. Imagine the level of control that gives you. And no more exceptions when being called in a deprecated way after changing your "signature" (argument count and meaning). This is something worth considering ;)
Here's what I do with unused arguments:
def f(a, *unused):
return a