From 3bb46c6a74cca600ec0a24a9c0339710c729103b Mon Sep 17 00:00:00 2001 From: SIVALANAGASHANKARNIVAS Date: Tue, 25 Nov 2025 17:24:13 +0530 Subject: [PATCH] Fix terminology: change 'parameters' to 'arguments' in MultiCall docs Fixes #140505 The xmlrpc.client.MultiCall documentation incorrectly used 'parameters' when it should say 'arguments'. The MultiCall object stores the call name and arguments (not parameters) since the call occurs through a getitem that returns a _MultiCallMethod callable with *args. --- Doc/library/xmlrpc.client.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/library/xmlrpc.client.rst b/Doc/library/xmlrpc.client.rst index e4912629aac6e0..7e511237a6abef 100644 --- a/Doc/library/xmlrpc.client.rst +++ b/Doc/library/xmlrpc.client.rst @@ -472,7 +472,7 @@ remote server into a single request [#]_. Create an object used to boxcar method calls. *server* is the eventual target of the call. Calls can be made to the result object, but they will immediately - return ``None``, and only store the call name and parameters in the + return ``None``, and only store the call name and arguments in the :class:`MultiCall` object. Calling the object itself causes all stored calls to be transmitted as a single ``system.multicall`` request. The result of this call is a :term:`generator`; iterating over this generator yields the individual