[Python-Dev] PEP 560: bases classes (original) (raw)
Ivan Levkivskyi levkivskyi at gmail.com
Thu Nov 16 07:22:43 EST 2017
- Previous message (by thread): [Python-Dev] PEP 560: bases classes / confusion
- Next message (by thread): [Python-Dev] PEP 560: bases classes / confusion
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 16 November 2017 at 07:56, Nick Coghlan <ncoghlan at gmail.com> wrote:
On 16 November 2017 at 04:39, Ivan Levkivskyi <levkivskyi at gmail.com> wrote:
Nick is exactly right here. Jim, if you want to propose alternative wording, then we could consider it.
Jim also raised an important point that needs clarification at the spec level: given multiple entries in "origbases" with mroentries methods, do all such methods get passed the same origbases tuple? Or do they receive partially resolved ones, such that bases listed before them have already been resolved to their MRO entries by the time they run. Yes, they all get the same initial bases tuple as an argument. Passing updated ones will cost a bit more and I don't think it will be needed (in the worst case a base can resolve another base by calling its mro_entries manually). I will clarify this in the PEP.
-- Ivan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20171116/91eeb041/attachment.html>
- Previous message (by thread): [Python-Dev] PEP 560: bases classes / confusion
- Next message (by thread): [Python-Dev] PEP 560: bases classes / confusion
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]