Mark Dickinson added the comment:

> If there are no such cases I think we should fix it.

Okay, but what exactly is this fixing?  I can't find any examples apart from 
max and min where the new error messages seem any better than the old.  Your 
first message talks about "a function that receives both positional and keyword 
arguments", by which I guess you mean 'both required and optional arguments';  
in any case, I can't find any such function (apart from max and min) that uses 
PyArg_ParseTuple.  So it seems to me that there's not actually any problem to 
be solved.

(And I think max and min probably need to be reworked to not use 
PyArg_ParseTuple at all.)


Python tracker <>
Python-bugs-list mailing list

Reply via email to