Message176068
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. |
|
Date |
User |
Action |
Args |
2012-11-21 18:02:33 | ezio.melotti | set | recipients:
+ ezio.melotti, mark.dickinson, chris.jerdonek |
2012-11-21 18:02:33 | ezio.melotti | set | messageid: <1353520953.68.0.39471187733.issue16515@psf.upfronthosting.co.za> |
2012-11-21 18:02:33 | ezio.melotti | link | issue16515 messages |
2012-11-21 18:02:33 | ezio.melotti | create | |
|