#31124: Model.get_FOO_display() does not work correctly with inherited choices.
-------------------------------------+-------------------------------------
Reporter: Yash Jhunjhunwala | Owner: George
| Popides
Type: Bug | Status: assigned
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
I've opened https://github.com/django/django/pull/12284 which provides a
fix for this, but also demonstrates how this issue will keep coming up...
My inclination here is to back-out the fix for #30931 and document
overriding `_get_FIELD_display()` for this kind of use-case.
My worry is that we get ever more baroque in handling the edge-cases... —
but we could take the fix here and draw a line at that point maybe?
--
Ticket URL: <https://code.djangoproject.com/ticket/31124#comment:12>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.3d4c83ecd18644266d95e47a19dc52a5%40djangoproject.com.
