Python: Functions
2026-02-21 02:58 Diff
https://hexlet.io/courses/python-functions/lessons/more-keyword-arguments/theory_unit

We can retrieve positional and named arguments in any number of *args.

Getting named arguments as dictionaries

Only named arguments can be obtained as a dictionary, which allows you to store the names in keys:

We can refer to an argument that receives this dictionary as kwargs (keyword arguments).

We write the keyword arguments after all the usual positional ones:

  • *args before the first argument with the default value
  • **kwargs after the last argument with the default value

Let us define a function that takes all kinds of arguments:

Do not worry. It is rare for a function to use all of these features in real-life code. Nevertheless, it is essential to understand how each type of argument declaration works and how to combine them.

Passing named arguments using dictionaries

As with positional arguments, named arguments can be passed to a function in bulk as a dictionary. To do this, you should put two asterisks before the dictionary. Here is an example:

As you can see, we also specified the regular named and wrapped arguments in a dictionary. It is both possible and convenient. Let us try to call the function f from the example at the beginning of the lesson with two sets of arguments:

  • The first one is for positional arguments
  • The second one is for named ones

Here is the code:

Notice how we constructed the dictionary. We did not write a literal. So, the dictionary looks even more like a stored set of arguments because we called the dict function with several named arguments.

You should also note that when replacing, these unfolding sets of arguments can be specified along with the corresponding type:

  • *positional with positional arguments
  • **named with named ones

Moreover, any named arguments must come after any positional arguments.

Using keyword-only arguments

Python 3 added the ability to mark the named arguments. So, we can call functions by passing those arguments by name. We can refer to them as keyword-only arguments.

We cannot pass them to the function as positional arguments. Here is an example:

The * separates ordinary arguments we can specify by name and position from strictly named arguments. This separator can only be used once in a single definition. And we cannot use it in functions with *args.

It is not logical, but that is how it happened. You can declare functions that take only strictly named arguments, but you should put an asterisk at the beginning of the argument list.

This example shows a way to describe arguments. The first argument is the name of the file to open. The file name is always present because you need to open something. Moreover, we usually associate its meaning with the function name. Therefore, this argument cannot be named.

But writable and binary are optional arguments. Which also take the seemingly meaningless values True and False. We will not please many people with a call open_file('raw.dat', True, True). Therefore, we declare the options such we can only give them explicitly.

Calling functions and the order of arguments

When calling functions, we have more freedom to set the order. We can mix single-named arguments with substitutions for positional sets. Here is an example of such a call:

Let us talk about another feature. It is a function with a signature like f(x, *args) where we cannot specify the x argument by name and expand the parameter set simultaneously. You cannot do anything like this: f(*foo, x=42).