Skip to content

Commit 220815b

Browse files
committed
gh-140505: update xmlrpc.client.rst to explain signature of complex types
1 parent 6b31ef6 commit 220815b

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

Doc/library/xmlrpc.client.rst

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -203,10 +203,13 @@ grouped under the reserved :attr:`~ServerProxy.system` attribute:
203203
Because multiple signatures (ie. overloading) is permitted, this method returns
204204
a list of signatures rather than a singleton.
205205

206-
Signatures themselves are restricted to the top level parameters expected by a
207-
method. For instance if a method expects one array of structs as a argument,
208-
and it returns a string, its signature is simply "string, array". If it expects
209-
three integers and returns a string, its signature is "string, int, int, int".
206+
Note that a signature does not give details of a complex type; it just gives the
207+
basic XML-RPC type — array or structure. This applies to both arguments and the
208+
return value. For example, if a method expects one array of structs as an argument
209+
and returns a string, its signature is simply "string, array". Here, "string" is
210+
the return type, and "array" indicates the argument type without showing the structure
211+
of its elements. If a method expects three integers and returns an array of strings,
212+
its signature is "array, int, int, int".
210213

211214
If no signature is defined for the method, a non-array value is returned. In
212215
Python this means that the type of the returned value will be something other

0 commit comments

Comments
 (0)