#30095: System check error for tuples in model field choices
-------------------------------------+-------------------------------------
Reporter: Pedro Marcondes | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: choices tuple | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
While it might require a lot of code duplication, a custom field that uses
tuples as valid values could override `Field._check_choices()`. I'm not
immediately convinced the issue is severe enough to require a patch for
Django 2.1 but we could simply remove the new validation as it's not
critical.
For this ticket's use case, `NumericRange` serialization is added in
Django 2.2 (#29738).
If we decide to take no action for Django 2.1, we could leave this ticket
open for someone to improve the validation. Actually, #20749 is already
open for that.
--
Ticket URL: <https://code.djangoproject.com/ticket/30095#comment:5>
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/063.f0880af342cd6de7c81939a05064068a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
