[issue16543] Use "positional arguments" in PyArg_UnpackTuple
Mark Dickinson
report at bugs.python.org
Fri Nov 23 19:29:40 CET 2012
Mark Dickinson added the comment:
Now that I look at uses of PyArg_UnpackTuple, I'm wondering whether this needs to be fixed at all. Apart from `max` and `min`, do you know of any other cases where this gives a misleading error message?
Almost all the uses I can find are for simple functions/methods where all arguments are positional-only. (Ex: range, pow, slice, dict.pop).
max and min *do* clearly need an error message fix.
(Apologies: I know it was me who suggested that PyArg_UnpackTuple needed fixing in the first place. But now I'm not sure that's true.)
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16543>
_______________________________________
More information about the Python-bugs-list
mailing list