Message294026
Cheryl: see also Issue 25777 and Issue 20751, both about the “super binding” under Invoking Descriptors.
Raymond: if you want to just pick parts of my patch, go for it. But I don’t understand your concern about explaining the MRO. I think it is important to explain which base classes are skipped, and which are searched. It is not just the type/subclass (super.__thisclass__) entry in the MRO that is skipped; this parameter determines the starting point, so the preceding entries are also skipped.
Another problem with referring to “getattr” is that it checks for instance attributes and custom __getattr__ and __getattribute__ implementations, but I don’t think “super” does any of that.
Looking at my patch now, I would propose that the exception message only be changed in the current (3.7) branch. |
|
Date |
User |
Action |
Args |
2017-05-20 10:32:19 | martin.panter | set | recipients:
+ martin.panter, rhettinger, r.david.murray, docs@python, Tapani Kiiskinen, cheryl.sabella |
2017-05-20 10:32:19 | martin.panter | set | messageid: <1495276339.05.0.214051194714.issue23674@psf.upfronthosting.co.za> |
2017-05-20 10:32:19 | martin.panter | link | issue23674 messages |
2017-05-20 10:32:18 | martin.panter | create | |
|