Ezio Melotti added the comment:

PyArg_UnpackTuple could be fixed to say "positional argument" (see attached 
patch (maybe this should be a separate issue)).
The error returned by max() is wrong because PyArg_UnpackTuple is used on the 
*args alone first, and it has no knowledge of the kwargs.
If PyArg_UnpackTuple is used to parse the *args then adding "positional" should 
solve the problem, however for this specific case the error would still be 
incorrect, because max also accepts more positional args.

Added file: http://bugs.python.org/file28065/issue16515-unpacktuple.diff

Python tracker <rep...@bugs.python.org>
Python-bugs-list mailing list

Reply via email to