#35976: Persist original Meta class on Options instances
-------------------------------------+-------------------------------------
Reporter: Tim McCurrach | Owner: (none)
Type: New feature | Status: closed
Component: Database layer | Version: 5.1
(models, ORM) |
Severity: Normal | Resolution: wontfix
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):
Hi Sarah,
Thanks for the speedy reply. Yes, I wasn't sure if it was a new feature or
clean-up either, but ended up thinking the same as you.
I started writing a post in the django forum, but as I was doing so,
reading the code again I realised the feature I was asking for actually
(more or less) already exists!!
(https://github.com/django/django/blob/c075d4c2c8cef3c9b28180c749d421c63544a9dd/django/db/models/options.py#L189-L191
)
My only question now, is should we document this? I'll re-open the ticket
as a documentation ticket and edit the description. If you think it's a
good idea to document it, I'd be happy to add something.
(Should I still start a thread on the django-forum for this, as even
though there are no code-changes I suppose this would be a new feature
from an external perspective. Please do let me know. Thanks)
--
Ticket URL: <https://code.djangoproject.com/ticket/35976#comment:2>
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/01070193a09f9b23-618aa7f8-1e9c-4bd4-aaa7-fb24d5a0fbb0-000000%40eu-central-1.amazonses.com.
