#32706: Ambiguity around field choices in the Model Field section
-------------------------------------+-------------------------------------
Reporter: Logan Kilpatrick | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Documentation | Version: 3.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
This is briefly explained in the same paragraph, just below the example:
> Though you can define a choices list outside of a model class and then
refer to it, defining the choices and names for each choice inside the
model class** keeps all of that information with the class that uses it,
and helps reference the choices** (e.g, Student.SOPHOMORE will work
anywhere that the Student model has been imported).
I think it's sufficient.
--
Ticket URL: <https://code.djangoproject.com/ticket/32706#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.b3606107e632f7e04b3e1b600ed550eb%40djangoproject.com.
