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 Ramchandra Apte
Recipients Ramchandra Apte
Date 2012-06-27.08:59:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340787562.9.0.381014932259.issue15201@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2012-06-27 08:59:22Ramchandra Aptesetrecipients: + Ramchandra Apte
2012-06-27 08:59:22Ramchandra Aptesetmessageid: <1340787562.9.0.381014932259.issue15201@psf.upfronthosting.co.za>
2012-06-27 08:59:22Ramchandra Aptelinkissue15201 messages
2012-06-27 08:59:21Ramchandra Aptecreate