FEEDBACK WANTED: Type/class unification

[Guido van Rossum]

Jiba <a11w at SoftHome.net> writes:

> I've just read http://www.python.org/2.2/descrintro.html :
> 
> > There's one very specific (and fortunately uncommon) bug that used
> > to go undetected, but which is now reported as an error:
> 
> class A:
> 	def foo(self): pass
> 
> class B(A): pass
> 
> class C(A):
> 	def foo(self):
> 		B.foo(self)
> 
> What about using wrappers ? Say, i've an instance o of class O. I can
> call :
> 
> O.method(o)
> 
> but what occurs if o is a wrapper to oo, an instance of O (Like a
> Bastion-wrapper) ?

That never worked, and still won't work.  I don't see that as a loss.

> Obviously, if o is a wrapper, we can call o.method(), but...

But what?

> By the way, it's interesting to notice that, for wrapper, o.method() is
> not the same think than O.method(o)...

In what sense?

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