[Python-Dev] Let's get rid of unbound methods
Jack Jansen
Jack.Jansen at cwi.nl
Wed Jan 5 00:01:34 CET 2005
On 4-jan-05, at 19:28, Guido van Rossum wrote:
> The
> extra type checking on the first argument that unbound methods are
> supposed to provide is not useful in practice (I can't remember that
> it ever caught a bug in my code)
It caught bugs for me a couple of times. If I remember correctly I was
calling methods of something that was supposed to be a mixin class but
I forgot to actually list the mixin as a base. But I don't think that's
a serious enough issue alone to keep the unbound method type.
But I'm more worried about losing the other information in an unbound
method, specifically im_class. I would guess that info is useful to
class browsers and such, or are there other ways to get at that?
--
Jack Jansen, <Jack.Jansen at cwi.nl>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma
Goldman
More information about the Python-Dev
mailing list