[issue38262] Mixins - super calls in bases of multiple-inheritance with different parameters

Steven D'Aprano added the comment: On Tue, Sep 24, 2019 at 08:54:49PM +, Arno-Can Uestuensoez wrote: > Or reduced to the focus of the actual issue and depicted the actual > passed parameters. See the following "Case 4 - same as > mixin_C_is_B0A1" for the essential question. > Case 4 - s

[issue38262] Mixins - super calls in bases of multiple-inheritance with different parameters

Arno-Can Uestuensoez added the comment: Fix two typos in my previous post: #>>> This basic diamond structure represents the call signatures: I: for D II: for B and C III: for A #<<< and #>>> The current implementation changes the routed method calls to the following call signa

[issue38262] Mixins - super calls in bases of multiple-inheritance with different parameters

Arno-Can Uestuensoez added the comment: Hi, first of all thank you both for the fast reply. The point is here, that the call routing and the parameter passing are intermixed. The MRO defines the call order, but does not define a signature change for the call within one inheritance layer. Al

[issue38262] Mixins - super calls in bases of multiple-inheritance with different parameters

Raymond Hettinger added the comment: > The oddity I came around is the simple case of mixins with > different parameters, where both are derived from 'object'. > It is obvious, that such a class has to comply to the parents > call interface - here object - when to be used standalone. BUT whe

[issue38262] Mixins - super calls in bases of multiple-inheritance with different parameters

Steven D'Aprano added the comment: Apologies for the Python 2.7 incompatible syntax, I hadn't noticed that you had selected 2.7. But since 2.7 (and 3.8) are in feature freeze, any behavoural changes can only apply to 3.9 or later. I'm afraid that you haven't explained why you think the code

[issue38262] Mixins - super calls in bases of multiple-inheritance with different parameters

Change by ppperry : -- type: compile error -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue38262] Mixins - super calls in bases of multiple-inheritance with different parameters

Arno-Can Uestuensoez added the comment: Hey, first of all thank you for the fast reply. Your examples reinforce exactly my issue. I prefer the KISS principle in providing isolated use-cases for transparency without extras. Which is seperated reduced flat calls only. The other point is, I de

[issue38262] Mixins - super calls in bases of multiple-inheritance with different parameters

Steven D'Aprano added the comment: I'm not an expert on super and multiple inheritance, but let me see if I can explain what is going on. (Hopefully an expert will correct me if I get something wrong.) 1. The class C(A_With_Arg, B_With_Arg) is straight-forward: the super call inside A passe

[issue38262] Mixins - super calls in bases of multiple-inheritance with different parameters

Steven D'Aprano added the comment: I took the health of my PC into my hands *smiles* and unzipped your test cases. I don't know .sh scripts well, so I didn't run that (and Windows users won't be able to run it), but I looked at the Python scripts, and I think I have duplicated your test case

[issue38262] Mixins - super calls in bases of multiple-inheritance with different parameters

Steven D'Aprano added the comment: Are your tests so huge that you need to gzip them before uploading? That makes them extremely difficult to read from the browser, and makes me extremely suspicious that this could be some form of zip bomb or other malware. Couldn't you upload a single .py f

[issue38262] Mixins - super calls in bases of multiple-inheritance with different parameters

New submission from Arno-Can Uestuensoez : The attached examples evaluate inheritance by mixins with different arameters and in different orders. The 'super()' call propagates the call resolution by definition to the next level, and cares about multiple inheritance as well as mixins. Where mixi