Why the use of *args in multiple-superclasses video?

The *args and **kwargs become catch-all bins for regular arguments and keyword arguments, respectively. Since the additional Agile and Sneaky class are unaware of what other arguments that might be passed to other classes in the Method Resolution Order chain, the safe approach is to use these catch-all parameters to hold all arguments, then pass on the all of these arguments to the next Class on the chain.

In an extended example, what would happen if a Agile was used in creating other classes that were based on, say, Monster or Politician or Animal? The Agile class has no idea what arguments are being passed in and which, if any, of the classes further down the MRO chain need which parameters. Using *args and **kwargs provides a convenient why to pass arguments along.

As an aside, it is the single-asterisk and double-asterisk that provides the functionality, not the "args" and "kwargs" text. The args and kwargs have been chosen as a recognizable convention, much like using "self" for class methods. It could just as easily been *things and **wordthings (and thismethod).

See more at python.org docs 3 tutorial controlflow keyword-arguments