c-api/call.rst:the arguments to an args tuple and kwargs dict anyway, then there is no point
c-api/call.rst:| Function                                 | callable         | args               | kwargs        |
library/tkinter.ttk.rst:      is specified then it is called with args if widget state matches
library/imaplib.rst:   Execute command args with messages identified by UID, rather than message
library/queue.rst:   Put *item* into the queue.  If optional args *block* is true and *timeout* is
library/queue.rst:   Remove and return an item from the queue.  If optional args *block* is true and
library/queue.rst:   The optional args *block* and *timeout* are ignored and only provided
library/queue.rst:   Remove and return an item from the queue.  If optional args *block* is true and
library/cmd.rst:   completing of commands args is done by calling :meth:`!complete_foo` with
library/string.rst:      passed to vformat.  The set of unused args can be calculated from these
library/argparse.rst:* ``'+'``. Just like ``'*'``, all command-line args present are gathered into a
library/argparse.rst:     >>> # parse the args and call whatever function was selected
library/argparse.rst:     >>> # parse the args and call whatever function was selected
library/unittest.mock-examples.rst:``side_effect`` will be called with the same args as the mock. This gives us an
library/multiprocessing.rst:      Remove and return an item from the queue.  If optional args *block* is
library/test.rst:   *kw* is extra keyword args to pass to :func:`subprocess.Popen`. Returns a
tutorial/errors.rst:   ...     print(inst)          # __str__ allows args to be printed directly,
using/configure.rst:   optimization configure args + the CPU architecture, and not all combinations