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 terry.reedy
Recipients benjamin.peterson, eric.araujo, gjb1002, ncoghlan, terry.reedy
Date 2010-10-01.18:09:31
SpamBayes Score 1.00466e-05
Marked as misclassified No
Message-id <1285956573.11.0.786084030874.issue9943@psf.upfronthosting.co.za>
In-reply-to
Content
FWIW 3.1 gives same message as 2.6. I have not installed 3.2a yet to check that.

Reporting of argument count mismatch has always been problematical, especially for methods. I almost think the message should be simplified to "Arguments passed do not match function signature." Programmers who do not immediately immediately see the problem (because they know the signature but made an inadvertent mistake) will have to check the signature anyway.

The alternative should be a clearer and more complete report than currently, which will take more than one line.
History
Date User Action Args
2010-10-01 18:09:33terry.reedysetrecipients: + terry.reedy, gjb1002, ncoghlan, benjamin.peterson, eric.araujo
2010-10-01 18:09:33terry.reedysetmessageid: <1285956573.11.0.786084030874.issue9943@psf.upfronthosting.co.za>
2010-10-01 18:09:31terry.reedylinkissue9943 messages
2010-10-01 18:09:31terry.reedycreate