Some functions produce wrong error messages in case they receive too many
keyword arguments:
- in Objects/exceptions.c - ImportError_init:
    >>> ImportError(1, 2, 3, 4, a=5, b=6, c=7)
    TypeError: ImportError() takes at most 2 arguments (3 given)
- in Python/bltinmodule.c - min_max:
    >>> min(1, 2, 3, 4, a=5, b=6, c=7)
    TypeError: function takes at most 2 arguments (3 given)
    >>> max(1, 2, 3, 4, a=5, b=6, c=7)
    TypeError: function takes at most 2 arguments (3 given)
- in Modules/itertoolsmodule.c - product_new:
    >>> itertools.product(0, a=1, b=2, c=3, d=4, e=5, f=6)
    TypeError: product() takes at most 1 argument (6 given)
- in Python/bltinmodule.c - builtin_print: 
    >>> print(0, a=1, b=2, c=3, d=4, e=5, f=6)
    TypeError: print() takes at most 4 arguments (6 given)

ISTM that changing these error messages to refer to 'keyword arguments' instead
of 'arguments' is a possible solution. (e.g. the last one would become
'print() takes at most 4 keyword arguments (6 given)'

To do that, I changed two 'takes at most' PyErr_Format calls in Python/getargs.c.
I ran the test suite, and it seems that this patch doesn't break anything.
The diff file is attached.
(I didn't open a PR before hearing your opinion, as ISTM that changing code in
getargs.c is a delicate thing.)

what do you think?

In all of these cases PyArg_ParseTupleAndKeywords() is used in uncommon way. These functions accept variable number of positional-only arguments, and PyArg_ParseTupleAndKeywords() is called with empty args tuple for parsing keyword arguments only. The patch uses a trick for detecting this case and generating more appropriate error message. Correct error message is generated in a normal case too.

LGTM. But it may be worth to add a short comment about the necessary of this special case. And please add tests for error messages in all of these functions. test_call looks appropriate place for them.

Could you please make a PR from your patch Oren?

I already wrote a patch, but I thought it would be better to wait until
#31236 is resolved.
this is because #31236 would change the error messages of min() and max(), and test_call tests exact error messages in
CFunctionCallsErrorMessages, which is where I thought the tests of this
issue should be added.

New changeset bf9075a0c55186d2f34df63e6c8512dd6414ff4b by Serhiy Storchaka (Oren Milman) in branch 'master':
bpo-31229: Fixed wrong error messages when too many keyword arguments are received. (#3180)
https://github.com/python/cpython/commit/bf9075a0c55186d2f34df63e6c8512dd6414ff4b

Thank you Oren for your contribution.