RetroSearch Browse

Fri May 21 03:23:15 CEST 2010 · https://mail.python.org/pipermail/python-dev/2010-May/100233.html

Floris Bruynooghe wrote:

> Not having looked at the code I don't know how hard it is for the code
> that raises this traceback to notice if it's a bound or unbound method
> tough.

The way things currently work, it would be quite difficult.
The exception is raised when attempting to call the function
underlying the bound method, at which point it can't be
distinguished from any other way of calling it.

However, it could be made to raise a special subclass of
TypeError that the bound method wrapper could catch and
replace with its own exception.

-- 
Greg

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-May/100233.html below:

[Python-Dev] Reasons behind misleading TypeError message when passing the wrong number of arguments to a method