This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients ezio.melotti, mark.dickinson, serhiy.storchaka
Date 2012-11-23.18:29:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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.)
Date User Action Args
2012-11-23 18:29:40mark.dickinsonsetrecipients: + mark.dickinson, ezio.melotti, serhiy.storchaka
2012-11-23 18:29:40mark.dickinsonsetmessageid: <>
2012-11-23 18:29:40mark.dickinsonlinkissue16543 messages
2012-11-23 18:29:40mark.dickinsoncreate