I think the following qualifies as a bug; I think the 
call to super(C, self).m() should cause an exception 
(the super_getattro search should not find the m in A 
if an m is defined in B):

>>> class A(object):
...     def m(self):
...         print 'A'
...
>>> class B(A):
...     m = property(lambda self: 'B')
...
>>> class C(B):
...     def m(self):
...         super(C, self).m()
...         print 'C'
...
>>> c = C()
>>> c.meth()
A
C

Logged In: YES 
user_id=35752

I agree.  This looks like a bug with super().

Logged In: YES 
user_id=6380

It would seem a bug, but according to the CVS log it's
intentional. typeobject.c 2.120 introduces an explicit check
that skips data descriptors (such as properties). The
motivation:

- super(C, C()).__class__ would return the __class__
attribute of C()
  rather than the __class__ attribute of the super object. 
This is
  confusing.  To fix this, I decided to change the semantics
of super
  so that it only applies to code attributes, not to data
attributes.
  After all, overriding data attributes is not supported
anyway.

So I think this is a feature after all.

Logged In: YES 
user_id=6380

Closing as Rejected.