You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
argument vs parameter confusion in XMLRPC client documentation #140505
But the arguments are stored, no the parameter (there's no parameter anyway as the call occur through a getitem that returns a _MultiCallMethod, itself using a call to be callable with *args, so there's no parameters at all (except *args).
So it should be:
store the call name and arguments
I leave this open for anyone wanting to tackle a very easy issue that can't break the prod.
Activity
pythongh-140505: Correct "parameters" to "arguments" in MultiCall doc
pythongh-140505: correct "parameters" to "arguments" in xmlrpc.client…
pythongh-140505: correct "parameter" to "argument" in ServerProxy met…
pythongh-140505: update xmlrpc.client.rst to explain signature of com…
Yuheng3107 commentedon Nov 18, 2025
Hi @JulienPalard I am willing to make this PR if it is still up for grabs
JulienPalard commentedon Nov 18, 2025
Hi @Yuheng3107 there's a PR opened about it that you can proofread: #140512
Fix terminology: change 'parameters' to 'arguments' in MultiCall docs
pythongh-140505: Fix 'parameters' to 'arguments' in xmlrpc.client.Mul…