[Python-ideas] Re: mro and super don't feel so pythonic

April 12, 2022


      On 2022-04-12 11:02, malmiteria  wrote:
...
My proposal would completely detach method resolution from calls to super.
essentially:
```
class A:
     val = 1
class B:
     val = 2
class C(A,B): pass
C.val # raises an explicitness required error
```
<snip>
If you think you can come up with code that would break under my proposal, hit me. I wanna have the least amount of breaking change.
You just showed an example in your own message.  The behavior of 
`C.val` is already defined in that case (it evaluates to 1).  If you 
change it so it now raises an error, that's a breaking change.

-- 
Brendan Barnwell
"Do not follow where the path may lead.  Go, instead, where there is no 
path, and leave a trail."
    --author unknown