I mean, overriding or augmenting is the solution in case of what i would call a conflict.
Essentially, a conflict araise when you're trying to access a method of a class that don't define it, and has multiple parent defining it. Todays solution would resolve the child method to the most left of its parent capable of delivering it, which does not make sense to me. If you want a real life example, I can't really share that code, but a coworker of mine once tried to reorder classes one of our class inherited from. His exact wording when doing it was "i just changed it to match the order django seems to prefer, it shouldn't break anything". I'll let you take a guess at if he was right or not. Multiple inheritance is fairly common in django, so if you want real life examples, you should find some in this community. I don't think what i'm looking for is different from inheritence, i think it's more a variant of the current way of doing things. Feel free to take a look at the readme of my github repository where i dive in some depths into my reasoning here : https://github.com/malmiteria/super-alternative-to-super _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/X3HXN7I7K3XNX7JISSZSRW7X7EIKLTEL/ Code of Conduct: http://python.org/psf/codeofconduct/
