#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
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
Comment:
OK, so the underlying issue here is that a tuple is not accepted as valid
in
[https://github.com/django/django/blob/87bf35abd3df1015d0c08a9251739d6c8454ab32/django/db/models/fields/__init__.py#L246-L247
the `is_value()` helper] used during the checks.
I’m not at all sure that’s a universally valid restriction on choices.
(???)
As such I’m inclined to Accept this as a Release Blocker on v2.1.
(“Behaviour change from previous version”)
Happy for input to the contrary. (!!!)
--
Ticket URL: <https://code.djangoproject.com/ticket/30095#comment:4>
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.d4919e6b3f61052dfab31c866e88fef3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
