#28033: Allow passing choices as a callable in a model field
-------------------------------------+-------------------------------------
Reporter: Ian Foote | Owner: Rémy
| Hubscher
Type: New feature | Status: assigned
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: choices | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Marco Silva):
Replying to [comment:10 kapil garg]:
> ''From
[https://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.Field.choices
django documentation]
>
>
> "Note that choices can be any iterable object – not necessarily a list
or tuple. This lets you construct choices dynamically. "--''
>
> I see now what is missing.
>
When building the patch doc changes, I found that particular line to be
problematic, because it is folowed by "But if you find yourself hacking
choices to be dynamic", so, does it let you contruct choices dynamically,
or you have to hack choices?
The current patch is just a way to cleanly have any iterator class(that
can be used dynamicaly and provide the desired effect) be added on to the
migrations file with its class name and not as the calculated choices
list.
--
Ticket URL: <https://code.djangoproject.com/ticket/28033#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 [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/067.9602a9159b01bc38b62aa0ff26319256%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
