Chris Angelico rosuav at gmail.com
Mon Apr 28 05:13:53 CEST 2014

• Previous message: [Python-Dev] Clarification on MRO when inheriting from builtin type.
• Next message: [Python-Dev] Clarification on MRO when inheriting from builtin type.
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Mon, Apr 28, 2014 at 12:59 PM, Paul Sokolovsky <pmiscml at gmail.com> wrote:
> From the output, "User" class as expected does not override
> list.append(), but does override list.__str__(). Is this behavior
> documented somewhere (complete arrangement)? What's the rationale
> behind it?

In Python 3.4 (don't know about other versions), list.__str__ doesn't
exist; when you call str([1,2,3]) it calls object.__str__. The MRO for
C is (C, list, User, object) so anything from list (eg append) takes
precedence over anything from User, but anything list doesn't have
will fall through to User before catching object.

ChrisA

---

• Previous message: [Python-Dev] Clarification on MRO when inheriting from builtin type.
• Next message: [Python-Dev] Clarification on MRO when inheriting from builtin type.
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list