#23250: Improve Error Message / Handling for ModelMultipleChoiceField and
queryset
attribute
--------------------------------------+------------------------------------
Reporter: wraus | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_docs: => 0
* component: Forms => Documentation
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
I have used this pattern before as well, however, I think it would be best
to document that `queryset` may be `None` if you want to specify it later.
Making it optional seems likely to trip up newbies.
--
Ticket URL: <https://code.djangoproject.com/ticket/23250#comment:1>
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.a8beb547613606bc9657243e304a8f8f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
