New submission from Ramchandra Apte <maniandra...@gmail.com>: C argument errors and Python arguments error are different. For example: all(4,4,4) Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: all() takes exactly one argument (3 given) def func(a):pass a(4,4) Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: func() takes exactly 1 positional argument (2 given) I do not know which error message is better. I think the second example's (func) error message is better. Though feel free to vote by commenting on this bug. Another example with not enough arguments given: hasattr(4) Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: hasattr expected 2 arguments, got 1 func() Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: func() takes exactly 1 argument (0 given) I don't know which of this error messages are better. You can vote on this by commenting.
---------- components: Interpreter Core messages: 164129 nosy: ramchandra.apte priority: normal severity: normal status: open title: C argument errors and Python arguments error are different type: behavior versions: Python 3.2 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15201> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
