homepage

Two new opcodes BUILD_MAP_UNPACK_WITH_CALL and BUILD_TUPLE_UNPACK_WITH_CALL (added in 3.5 and 3.6) have too long names (26 and 28 characters). This exceeds the width of the opcode names in the dis module (20 characters). Increasing the width of the column will make opcode arguments too distant from opcode names, that will decrease readability. The better solution would be renaming these two opcodes.
They are used for merging iterables and mappings of positional and keyword arguments when used var-positional (*args) and var-keyword (**kwargs) arguments. Maybe new names should reflect this.
>>> dis.dis('f(a, b, *args, x=x, y=y, **kw)')
 1 0 LOAD_NAME 0 (f)
 2 LOAD_NAME 1 (a)
 4 LOAD_NAME 2 (b)
 6 BUILD_TUPLE 2
 8 LOAD_NAME 3 (args)
 10 BUILD_TUPLE_UNPACK_WITH_CALL 2
 12 LOAD_NAME 4 (x)
 14 LOAD_NAME 5 (y)
 16 LOAD_CONST 0 (('x', 'y'))
 18 BUILD_CONST_KEY_MAP 2
 20 LOAD_NAME 6 (kw)
 22 BUILD_MAP_UNPACK_WITH_CALL 2
 24 CALL_FUNCTION_EX 1
 26 RETURN_VALUE

If we used the names from inspect.Parameter.kind (https://docs.python.org/3/library/inspect.html#inspect.Parameter.kind) these would become:
* BUILD_VAR_POSITIONAL
* BUILD_VAR_KEYWORD
which would be 20 and 17 letters long, respectively.
I think that would also make the disassembled bytecode more self-explanatory:
>>> dis.dis('f(a, b, *args, x=x, y=y, **kw)')
 1 0 LOAD_NAME 0 (f)
 2 LOAD_NAME 1 (a)
 4 LOAD_NAME 2 (b)
 6 BUILD_TUPLE 2
 8 LOAD_NAME 3 (args)
 10 BUILD_VAR_POSITIONAL 2
 12 LOAD_NAME 4 (x)
 14 LOAD_NAME 5 (y)
 16 LOAD_CONST 0 (('x', 'y'))
 18 BUILD_CONST_KEY_MAP 2
 20 LOAD_NAME 6 (kw)
 22 BUILD_VAR_KEYWORD 2
 24 CALL_FUNCTION_EX 1
 26 RETURN_VALUE

I like the names BUILD_VAR_POSITIONAL and BUILD_VAR_KEYWORD.
The downside is that this breaks relations between them and very similar opcodes BUILD_TUPLE_UNPACK and BUILD_MAP_UNPACK. The only differences between BUILD_*_UNPACK and BUILD_*_UNPACK_WITH_CALL opcodes is that the latter takes a function name from the stack for error message and BUILD_MAP_UNPACK_WITH_CALL doesn't allow key duplications in contrary to BUILD_MAP_UNPACK. But the names BUILD_TUPLE_UNPACK and BUILD_MAP_UNPACK doesn't look very good too.

I think it should be sufficient connection to describe the link in the documentation as:
* BUILD_VAR_POSITIONAL: a variant of BUILD_TUPLE_UNPACK tailored specifically for use in function calls
* BUILD_VAR_KEYWORD: a variant of BUILD_MAP_UNPACK tailored specifically for use in function calls
The BUILD_*_UNPACK documentation could also point to their relevant function call counterpart: "Note: function calls do not use this opcode, they use the specialized BUILD_VAR_<kind>".

I have created a pull request for this issue. Please take a look.

Reviewing this again now, I think my previous naming suggestion is problematic, as it encourages conflating two different concepts that use similar syntax:
* collecting arbitrary positional parameters in a tuple (VAR_POSITIONAL) or arbitrary keyword parameters in a dictionary (VAR_POSITIONAL, VAR_KEYWORD)
* unpacking function arguments from iterables (BUILD_VAR_POSITIONAL) or mappings (BUILD_VAR_KEYWORD)
I think the fix for that error is straightforward though: replace "VAR" with "ARG" in the new opcode names, giving:
* BUILD_ARG_POSITIONAL
* BUILD_ARG_KEYWORD
That should also read nicely with Zackery's documentation updates.

These opcodes are always used with CALL_FUNCTION_EX (which can be used also without any of them).
f(*a, *b, **c, **d)
 1 0 LOAD_NAME 0 (f)
 2 LOAD_NAME 1 (a)
 4 LOAD_NAME 2 (b)
 6 BUILD_TUPLE_UNPACK_WITH_CALL 2
 8 LOAD_NAME 3 (c)
 10 LOAD_NAME 4 (d)
 12 BUILD_MAP_UNPACK_WITH_CALL 2
 14 CALL_FUNCTION_EX 1
I though about naming CALL_FUNCTION_EX as CALL_FUNCTION_VAR in 3.6, but this name was used in pre-3.6 bytecode with different semantic. Now I think there is smaller change of confusion, so it can be renamed to CALL_FUNCTION_VAR or something other.

So we'd be going with a naming convention where "VAR" corresponds to the star syntax, and whether it means packing or unpacking, or refers to arguments or parameters is context dependent?
I could definitely support that, given that the ambiguity already exists at the Python syntax level.

Serhiy, may I close this issue please?
Since 3.10, those long opcodes no longer exist. Issue39320 removed BUILD_TUPLE_UNPACK_WITH_CALL and BUILD_MAP_UNPACK_WITH_CALL from the compiler. The new opcodes have shorter names.

Sure.