I’m looking into Django ticket #34555 regarding ModelBase not collecting
model fields added via init_subclass.
My goal is not to push for an immediate fix, but to:
reproduce the issue with a minimal test case,
explore a small proof-of-concept (PoC),
and document why this is currently difficult or blocked
(e.g. backward compatibility concerns).
I’m happy to start with a test-only contribution if that’s considered
useful at this stage, or to share findings back here before proposing
any changes.
Any guidance on the preferred scope or next steps would be appreciated.
I think that particular ticket is not blocked on needing a test case or documentation (the discussion has a LOT of info and context). A PoC that shows a path forward that addresses the already covered concerns would be the next step. However, it’s definitely an advanced ticket, so I would advise against it for a first contribution!
Great approach. A minimal test case and small PoC will really help clarify the issue and any constraints. Sharing findings first sounds like a very constructive next step.
Thanks for the clarification — that makes sense.
I’ll take a step back and treat this as an exploratory PoC only, focusing on understanding the constraints and documenting findings rather than proposing a fix.
I’ll share any concrete observations back here before considering anything further.