From a190d7b475c133fec79da0ddb205f6bad387175c Mon Sep 17 00:00:00 2001 From: Klu1d Date: Thu, 23 Oct 2025 20:06:44 +0300 Subject: [PATCH 1/4] gh-140505: Correct "parameters" to "arguments" in MultiCall doc --- 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 547cb50be78a78..e5cdff6188680a 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 From 726c71674f4812a7a0c11bad47a5c1e77971df19 Mon Sep 17 00:00:00 2001 From: Klu1d Date: Thu, 23 Oct 2025 21:17:12 +0300 Subject: [PATCH 2/4] gh-140505: correct "parameters" to "arguments" in xmlrpc.client module description --- 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 e5cdff6188680a..817b9adb9132d4 100644 --- a/Doc/library/xmlrpc.client.rst +++ b/Doc/library/xmlrpc.client.rst @@ -15,7 +15,7 @@ -------------- XML-RPC is a Remote Procedure Call method that uses XML passed via HTTP(S) as a -transport. With it, a client can call methods with parameters on a remote +transport. With it, a client can call methods with arguments on a remote server (the server is named by a URI) and get back structured data. This module supports writing XML-RPC client code; it handles all the details of translating between conformable Python objects and XML on the wire. From 6b31ef6d39b733d736d382ba120e7b7992d0b036 Mon Sep 17 00:00:00 2001 From: Klu1d Date: Sat, 25 Oct 2025 17:54:00 +0300 Subject: [PATCH 3/4] gh-140505: correct "parameter" to "argument" in ServerProxy methods --- Doc/library/xmlrpc.client.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Doc/library/xmlrpc.client.rst b/Doc/library/xmlrpc.client.rst index 817b9adb9132d4..bfc75776e11717 100644 --- a/Doc/library/xmlrpc.client.rst +++ b/Doc/library/xmlrpc.client.rst @@ -195,7 +195,7 @@ grouped under the reserved :attr:`~ServerProxy.system` attribute: .. method:: ServerProxy.system.methodSignature(name) - This method takes one parameter, the name of a method implemented by the XML-RPC + This method takes one argument, the name of a method implemented by the XML-RPC server. It returns an array of possible signatures for this method. A signature is an array of types. The first of these types is the return type of the method, the rest are parameters. @@ -204,7 +204,7 @@ grouped under the reserved :attr:`~ServerProxy.system` attribute: a list of signatures rather than a singleton. Signatures themselves are restricted to the top level parameters expected by a - method. For instance if a method expects one array of structs as a parameter, + method. For instance if a method expects one array of structs as a argument, and it returns a string, its signature is simply "string, array". If it expects three integers and returns a string, its signature is "string, int, int, int". @@ -215,7 +215,7 @@ grouped under the reserved :attr:`~ServerProxy.system` attribute: .. method:: ServerProxy.system.methodHelp(name) - This method takes one parameter, the name of a method implemented by the XML-RPC + This method takes one argument, the name of a method implemented by the XML-RPC server. It returns a documentation string describing the use of that method. If no such string is available, an empty string is returned. The documentation string may contain HTML markup. From 220815be9841e93352c46f91c53e48a73cc3e445 Mon Sep 17 00:00:00 2001 From: Klu1d Date: Mon, 27 Oct 2025 19:49:06 +0300 Subject: [PATCH 4/4] gh-140505: update xmlrpc.client.rst to explain signature of complex types --- Doc/library/xmlrpc.client.rst | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/Doc/library/xmlrpc.client.rst b/Doc/library/xmlrpc.client.rst index bfc75776e11717..b47889749835cd 100644 --- a/Doc/library/xmlrpc.client.rst +++ b/Doc/library/xmlrpc.client.rst @@ -203,10 +203,13 @@ grouped under the reserved :attr:`~ServerProxy.system` attribute: Because multiple signatures (ie. overloading) is permitted, this method returns a list of signatures rather than a singleton. - Signatures themselves are restricted to the top level parameters expected by a - method. For instance if a method expects one array of structs as a argument, - and it returns a string, its signature is simply "string, array". If it expects - three integers and returns a string, its signature is "string, int, int, int". + Note that a signature does not give details of a complex type; it just gives the + basic XML-RPC type — array or structure. This applies to both arguments and the + return value. For example, if a method expects one array of structs as an argument + and returns a string, its signature is simply "string, array". Here, "string" is + the return type, and "array" indicates the argument type without showing the structure + of its elements. If a method expects three integers and returns an array of strings, + its signature is "array, int, int, int". If no signature is defined for the method, a non-array value is returned. In Python this means that the type of the returned value will be something other