#31261: Add support for defining models.Choices fields with dict, tuple, set and
list values.
-------------------------------------+-------------------------------------
Reporter: Tom Forbes | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
> Perhaps this ticket should be more general: "Support for defining model
choice groups in Enums"? The exact implementation might vary, but I think
the overall goal is something we should work towards.
Yes. I agree with that sentiment. Grouping (both kinds) is useful. I guess
the `needsinfo` here just means Proof-of-concept to push is forwards.
--
Ticket URL: <https://code.djangoproject.com/ticket/31261#comment:5>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/061.ec7e976119ab87a48827661751d01e50%40djangoproject.com.
