RetroSearch Browse

Wed Jan 5 19:10:32 CET 2005 · https://mail.python.org/pipermail/python-dev/2005-January/050700.html

> Um, isn't all this stuff going to be more complicated and spread out over
> more of the code than just leaving unbound methods in place?

Well, in an early version of Python it was as simple as I'd like ot to
be again: the instancemethod type was only used for bound methods
(hence the name) and C.f would return same the function object as
C.__dict__["f"]. Apart from backwards compatibility with all the code
that has grown cruft to deal with the fact that C.f is not a function
object, I still see no reason why the current state of affairs is
better.

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)

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

Showing content from https://mail.python.org/pipermail/python-dev/2005-January/050700.html below:

[Python-Dev] Let's get rid of unbound methods