#16006: Make cache lazy to allow test runners to switch cache backends
-------------------------------------+-------------------------------------
Reporter: brianjaystanley | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: 1.3
Component: Core (Cache system) | Resolution: wontfix
Severity: Normal | Triage Stage: Design
Keywords: | decision needed
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* status: new => closed
* resolution: => wontfix
Comment:
The argument in favor of this change is:
> Switching cache backends at runtime would be useful in test runners, in
order to be able to test caching-related functionality without populating
a production cache.
Running tests on a production server, with production settings, certainly
isn't something we want to encourage. You should use a different settings
file, or even better, a clone of your production environment.
--
Ticket URL: <https://code.djangoproject.com/ticket/16006#comment:5>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
