#34388: Added support for direct usage of Choices classes on model fields
-------------------------------------+-------------------------------------
Reporter: T. Franzel | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
> Passing a Choices class makes sense, instead of doing the strange
choices=MyChoices.choices manipulation
I think that's right — it would feel nice.
But we're not going to remove the support for lists of pairs...
(If we loosen here then typing for choices goes from list of pairs to list
of pair OR Choices subclass, which I can imagine folk complaining about.)
Then there's the separate point about storing a reference that we're not
going to use.
Let's close then. Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/34388#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 on the web visit
https://groups.google.com/d/msgid/django-updates/01070186c542200d-2f3d6b44-9a2c-41bc-b2e3-3005d36d2493-000000%40eu-central-1.amazonses.com.
