#35976: Persist original Meta class on Options instances
-------------------------------+--------------------------------------
Reporter: Tim McCurrach | Owner: (none)
Type: Uncategorized | Status: new
Component: Documentation | Version: 5.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Tim McCurrach):
Just to play devils advocate here:
Reading the comment above where it is defined, documenting the attribute
would potentially represent a change in purpose for the variable. At the
moment it exists to aid with serialisation of the model, which would be
distinct to a reference for users to take advantage of.
Also, looking at [https://docs.djangoproject.com/en/5.1/ref/models/options
/#read-only-meta-attributes the docs], there are currently only 2
attributes listed under read-only attributes, and there are definitely
others defined on `Options` that could go there. So there is also a
question of precedent here.
None-the-less, I think it would be quite a useful thing to know about. I
could go either way on this.
--
Ticket URL: <https://code.djangoproject.com/ticket/35976#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070193a0a7cdb5-4dc8781e-bd6c-4a60-9bf8-44d1a763619c-000000%40eu-central-1.amazonses.com.
