#24561: Allow model field choices to accept callables.
-------------------------------------+-------------------------------------
Reporter: EnTeQuAk | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(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
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: => 1
* component: Core (System checks) => Database layer (models, ORM)
* needs_tests: => 0
* version: 1.8 => master
* needs_docs: => 0
* type: Bug => New feature
* stage: Unreviewed => Accepted
Comment:
It was added for `django.forms.ChoiceField`, but not model field
`choices`. It might be a reasonable feature request, but it needs to be
implemented. It might cause some difficulty in migrations, but I will
accept the ticket if someone wants to investigate the possibility.
--
Ticket URL: <https://code.djangoproject.com/ticket/24561#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.282c9d507b472e04a1d06aa1b17f2dc1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.