← board

class D(B, C): does not parse

class A:
    def who(self):
        return "A"

class B(A):
    def who(self):
        return "B"

class C(A):
    def who(self):
        return "C"

class D(B, C):     # <-- error: unexpected token, at the ','
    pass

print(D().who())   # CPython: B  (MRO: D, B, C, A)



pascal26:22: error: unexpected token
  near:    D  B >>>  C

Single inheritance works. Only the comma is rejected, so the class header parser evidently takes exactly one base.

Why this is prio 40 and not higher

It fails loudly at compile time, and single inheritance covers the overwhelming majority of real NilPy code. But it blocks every mixin idiom, which is how a lot of ordinary Python is structured, so it will keep being hit by corpus work.

The real cost is the MRO, not the parse

Accepting the comma is the easy half and is NOT the feature. Python resolves attributes by C3 linearisation, so D().who() must give "B" — and with a diamond (both B and C deriving from A) the order is D, B, C, A, which is observable whenever two bases define the same name. The underlying Pascal object model is single-inheritance, so a second base cannot be a real parent.

Options, roughly in order of honesty:

  1. Full C3 with explicit dispatch — flatten the linearisation at compile time and resolve each attribute to the winning definition. Correct, and the most work.
  2. Second base as a delegate — real inheritance from the first base, and attributes not found there forwarded to an embedded instance of the second. Handles mixins, gets the diamond wrong in the case where C3 would pick C over an inherited-from-A member of B.
  3. Refuse a second base explicitly — replace "unexpected token" with a diagnostic naming multiple inheritance. Cheap, honest, and strictly better than today's error, which reads like a parser bug.

Option 3 is worth doing immediately regardless of which of 1/2 is chosen later. Do NOT accept the comma and silently ignore the second base: that turns a compile error into a wrong method being called at run time.

Gate

A .npy diffed against CPython covering: a plain mixin (bases with disjoint methods), a diamond where the MRO is observable, and isinstance against both bases.

2026-08-04 — option 3 landed; the FEATURE is still open

Did the part this ticket said was "worth doing immediately regardless of which of 1/2 is chosen later", and deliberately nothing more.

class D(B, C): now says what is actually wrong:

Nil Python: multiple inheritance is not supported — `class D` names more than
one base. Python resolves these by C3 linearisation and the object model here is
single-inheritance, so a second base cannot be honoured; it is refused rather
than silently ignored. Use single inheritance, or compose: hold the would-be
second base as a field and forward to it

instead of unexpected token pointing at the comma, which read like a parser bug rather than a missing feature — and left the reader with no idea whether to work around it or file it.

The message states the constraint (single-inheritance object model), why the comma cannot simply be accepted (C3 is observable the moment two bases define the same name), and the workaround, so it is actionable without reading this ticket.

Deliberately NOT done: accepting the comma. The ticket is explicit and it is right — taking a second base and dropping it converts a compile error into the WRONG METHOD being called at run time, which is worse than not supporting the feature.

Single inheritance, class E(Exception), and dotted bases are unchanged (verified against CPython). tools/gate.sh quick GREEN, self-host byte-identical.

Ticket stays OPEN for option 1 (full C3 with explicit dispatch) or option 2 (second base as a delegate). Nothing about that choice is foreclosed by this; the diagnostic is what a reader hits either way until one of them lands.

2026-08-08 — RE-SCOPED by decision: FLATTEN. The option list above is superseded

[[decide-nilpy-multiple-inheritance-c3-or-delegate]] is decided and the answer is none of the three options this ticket lists. Do not implement 1, 2 or 3 from the section above; they are kept only as the record of how the question was framed.

Build this instead — v1:

  1. Flatten. Accept the comma; copy each extra base's methods into the derived class, compiled with self = the DERIVED class, conflicts resolved in C3 left-to-right order (first base wins). Class-level attributes on the flattened base come along too — and that touches the class-attribute lowering reworked 2026-08-07 (shared slot vs copy-at-construction), so verify that interaction rather than assuming it.
  2. Refuse the diamond. Two bases sharing an ancestor: C3 gives ONE shared ancestor, naive flattening can give two, and the state then diverges. Compile error naming it, in the spirit of the diagnostic that already landed here.
  3. Diagnose super() across a flattened base. CPython routes super().__init__() in the first base to the SECOND base via the MRO; a flattened body goes to its own base instead. Silence here would be a wrong call at run time, so it must be a compile-time error or warning.

Explicitly NOT in v1: isinstance(d, C) will answer False where CPython says True. That is the known cost, it is loud rather than silent, and it is fixed later by synthesising an interface per flattened base — which rides the RTTI interface table and IMT that already exist (PXX_RTTI_PARENT is a single parent pointer, but every implemented interface already gets a 24-byte RTTI entry).

Why not delegate — the option this ticket previously recommended: a mixin's self IS the derived object in Python, so an embedded instance cannot see the host's attributes and the common mixin breaks. Full reasoning in the decision.

Gate (unchanged in spirit, sharpened)

A .npy diffed against CPython covering: a plain mixin (disjoint methods), a mixin whose method reads an attribute of the DERIVED class (the case delegation would fail), left-to-right conflict resolution where both bases define the same method, class attributes carried from a flattened base — plus {%FAIL}-style checks that the diamond and a super() chain across a flattened base are refused with their own messages.