On 4/13/2022 7:22 AM, malmiteria wrote:
Eric V. Smith writes:
My suggestion is to rework your proposal to not break any existing code I've been doing that already, and i'll keep doing it, i'm very aware of this constraint.
What are the biggest breaking change i haven't covered yet, in your opinion? If you can think of a few that seem way too bad please let me know.
I'm not tracking your exact proposal very closely. The problem would be any code that uses existing syntax and raises the exception you're proposing when an attribute is defined in multiple base classes. I can't find the exact name you're proposing. I don't think we need to find existing code that meets this criteria. It doesn't matter if it requires diamond inheritance, non-diamond inheritance, or whatever. If the exception can possibly be raised in code that's valid in any currently supported python version, then you have a backward compatibility problem. Eric