#30095: System check error for tuples in model field choices
-------------------------------------+-------------------------------------
Reporter: Pedro Marcondes | Owner: CHANDAN
| PRAKASH
Type: Bug | Status: assigned
Component: Database layer | Version: 2.1
(models, ORM) |
Severity: Normal | 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 Carlton Gibson):
Hi Chandan.
First step is to read the contributing guide:
https://docs.djangoproject.com/en/dev/internals/contributing/
Then your best bet, I think, is to take the test case I used and add it to
the existing postgres test cases (you’ll need to have a look around as to
where is best).
You’ll need to run against PostgreSQL to test. See
https://docs.djangoproject.com/en/2.0/topics/testing/overview/#the-test-
database
Then if you run the test suite you’ll see a failure. The test doesn’t
currently pass. The task is to make it pass.
As per the discussion, implementing `RangeField._check_choices()` to
override `Field._check_choices()` is the likely way forward.
Once you have something, even if not perfect, open a PR on GitHub and we
can provide feedback.
Welcome aboard!
--
Ticket URL: <https://code.djangoproject.com/ticket/30095#comment:9>
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.233c31cf4ed4c00e3b817cdc818ee948%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
