Ezio Melotti added the comment:

> do you know of any other cases where this gives a misleading error message?

Actually my concern was about cases where the new error might be 
wrong/misleading, but I haven't checked yet.  If there are no such cases I 
think we should fix it; the error message will be better in the few cases we 
have in the stdlib and for all the external libs that are using the function.

Another thing that I haven't checked is if there are similar functions (e.g. to 
parse kwargs) that needs the same treatment (#16520 might be one such example).


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

Reply via email to