Lines Matching refs:positional

458    parrot(1000)                                          # 1 positional argument
462    parrot('a million', 'bereft of life', 'jump')         # 3 positional arguments
463    parrot('a thousand', state='pushing up the daisies')  # 1 positional, 1 keyword
472 In a function call, keyword arguments must follow positional arguments.
492 receives a :ref:`tuple <tut-tuples>` containing the positional
551 positional-only, positional-or-keyword, and keyword-only. Keyword parameters
566 as *positional-only*. If *positional-only*, the parameters' order matters, and
569 separate the positional-only parameters from the rest of the parameters.
570 If there is no ``/`` in the function definition, there are no positional-only
573 Parameters following the ``/`` may be *positional-or-keyword* or *keyword-only*.
613 The second function ``pos_only_arg`` is restricted to only use positional
630    TypeError: kwd_only_arg() takes 0 positional arguments but 1 was given
641    TypeError: combined_example() takes 2 positional arguments but 3 were given
655 Finally, consider this function definition which has a potential collision between the positional a…
669 But using ``/`` (positional only arguments), it is possible since it allows ``name`` as a positiona…
676 In other words, the names of positional-only parameters can be used in
689 * Use positional-only if you want the name of the parameters to not be
692   is called or if you need to take some positional parameters and arbitrary
697 * For an API, use positional-only to prevent breaking API changes
721 keywords rather than positional arguments. ::
737 but need to be unpacked for a function call requiring separate positional
868 following example has a positional argument, a keyword argument, and the return