#29549: Document that Field.choices are enforced by model validation
-------------------------------------+-------------------------------------
Reporter: Evgeny Arshinov | Owner: Tim
Type: | Graham
Cleanup/optimization | Status: closed
Component: Documentation | Version: 1.11
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Evgeny Arshinov):
Replying to [comment:8 Tim Graham]:
> Absent some proposal of the changes Django should make (not clear to
me), opening a Trac ticket isn't the way to proceed. This ticket has been
repurposed for further documentation. If we decide to make some other
change, we'll open a new ticket. Feel free to write to the
DevelopersMailingList if you have some ideas.
Hello Tim,
I don't have a proposal except starting to support model validation on
save. I am not familiar with Django's inner workings to suggest any
concrete steps.
However, I am inclined to think that presence of a problem should be
enough for a ticket to be opened, whether or not there is a concrete
change proposal. The question about incomplete validation comes up fairly
regularly i.e. on StackOverflow, and a ticket in the official bug tracker
could be a good reference source and an indicator of the fact that Django
developers are aware of the problem and maybe fix it someday. Also, a
ticket can be subscribed to. I guess I am not the only one who prefers a
ticket to numerous disorganized discussions on StackOverflow and other
forums.
I understand that what I have written might contradict the code of
practice established in Django. If it is so, I am fine with closing the
discussion since I have nothing more to suggest.
--
Ticket URL: <https://code.djangoproject.com/ticket/29549#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.a4a9d750884e6a0dfa06f0ce0e99aa5f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
