Python Lambda冗余参数合规写法咨询：避免重复下划线报错

Great question! I totally get why you want to clearly flag those unused parameters—readability is critical when you’re stuck with a function signature dictated by a library. Let’s walk through why your initial approach fails and the clean fixes you can use:

First, why does lambda _, _, z: ... throw an error? Python doesn’t allow duplicate parameter names in the same function scope (whether it’s a lambda or a regular def), so reusing _ triggers a syntax error. But there are several workarounds that keep the "unused parameter" intent clear while staying concise:

方案1：带数字后缀的下划线（直观标记参数位置） #

Add numeric suffixes to the underscores to avoid duplication. This follows the familiar throwaway variable convention and makes the position of unused parameters explicit:

f = lambda _1, _2, z: some_operation(z)

Anyone reading this will instantly recognize the first two parameters are redundant, and the numbers tie directly to their order in the signature.

方案2：带参数标识的下划线（语义更明确） #

If you want to link unused parameters back to their original names (x and y), use underscore-prefixed names. This is still concise but adds a layer of clarity for anyone familiar with the library’s required signature:

f = lambda _x, _y, z: some_operation(z)

This tells readers "these are the x and y parameters the library expects, but we’re not using them."

方案3：单下划线+双下划线（沿用惯例的简洁写法） #

Double underscores (__) are valid parameter names in Python and are widely accepted as secondary throwaway variables. This keeps the underscore pattern you prefer without duplication:

f = lambda _, __, z: some_operation(z)

Most Python developers will immediately recognize __ as another unused parameter, so this feels natural while avoiding syntax errors.

示例验证 #

Let’s test these with a simple some_operation to confirm they work as expected:

def some_operation(z):
    return z * 3

# Any of the above lambda definitions will work here
print(f(10, 20, 4))  # Output: 12

All these solutions hit your requirements: they use lambda for brevity, clearly mark unused parameters, and avoid syntax issues. Pick the one that aligns best with your team’s readability preferences!

内容的提问来源于stack exchange，提问作者Captain Trojan