#22838: Deprecate ModelChoiceField.cache_choices
-------------------------------------+-------------------------------------
Reporter: mjtamlyn | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Forms | Resolution:
Severity: Normal | Triage Stage: Ready for
Keywords: | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by russellm):
This was raised on IRC, so weighing in for posterity: The cache behaviour
implemented by this feature is naive (since it won't be shared between web
servers). Since this isn't documented, and isn't used anywhere, I'm OK
with an expedited deprecation cycle (i.e., 1 release with a visible
warning, then kill it).
There's a reasonable argument for providing caching for query-backed
ModelChoice fields, but it should be using an interface to the cache
backend, not implementing an in-memory cache. However, that's a separate
feature.
--
Ticket URL: <https://code.djangoproject.com/ticket/22838#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/066.47be1af908933f397153a20a28a8bbec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
