#29247: A custom blank value in model field choices doesn't work when using
named
groups
-------------------------------------+-------------------------------------
Reporter: orlnub123 | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: choices | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"21420096c4db78ccb8f549a29d662cff870d363c" 2142009]:
{{{
#!CommitTicketReference repository=""
revision="21420096c4db78ccb8f549a29d662cff870d363c"
Fixed #29247 -- Allowed blank model field choice to be defined in nested
choices.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29247#comment:3>
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.29ba4a9f1cba2fa8404ba01cd46e0a09%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
