Author scoder
Recipients Matthias Braun, gvanrossum, petr.viktorin, scoder
Date 2020-06-21.20:55:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1592772907.42.0.551232229548.issue39960@roundup.psfhosted.org>
In-reply-to
Content
This SO answer by Martijn Pieters explains the background:

https://stackoverflow.com/a/44854477

and links to the original python-dev discussion:

https://mail.python.org/pipermail/python-dev/2003-April/034535.html

The current implementation checks that the function being called is the one defined in the first non-heap type up the hierarchy. As long as heap types are only Python types, this is the first builtin/native/C-implemented (super)type. With extension types as heap types, however, it's no longer necessarily the type that defines the correct slot function.

IMHO, Greg Ewing gives the right direction here:

https://mail.python.org/pipermail/python-dev/2003-April/034569.html

> Providing some way for objects to prevent superclass
> methods from being called on them when they're not looking

So, I think we should do something like walking up the hierarchy to find the C function in it that is currently being called, and then check if it's the one we would expect or if a subclass defines a different one. The current check does not bother to search and just assumes that it knows which (super)type defines the right function to call.
History
Date User Action Args
2020-06-21 20:55:07scodersetrecipients: + scoder, gvanrossum, petr.viktorin, Matthias Braun
2020-06-21 20:55:07scodersetmessageid: <1592772907.42.0.551232229548.issue39960@roundup.psfhosted.org>
2020-06-21 20:55:07scoderlinkissue39960 messages
2020-06-21 20:55:07scodercreate