#16006: Make cache lazy to allow test runners to switch cache backends
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
brianjaystanley | Status: new
Type: | Component: Core (Cache system)
Cleanup/optimization | Severity: Normal
Milestone: | Keywords:
Version: 1.3 | Has patch: 1
Resolution: | Needs tests: 0
Triage Stage: | Easy pickings: 0
Unreviewed |
Needs documentation: 0 |
Patch needs improvement: 0 |
-------------------------------------+-------------------------------------
Changes (by brianjaystanley):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
The patch also allows any cache backend loaded through get_cache to
register a request_finished signal handler if it needs to. In the
original, the signal registration is only available for the default cache,
so loading another cache that needs to do cleanup will not register its
handler. In the patch, registration will happen later because of the cache
being lazy, but that should be fine since no cache backend should need to
receive request_finished signals if it was never even loaded.
--
Ticket URL: <http://code.djangoproject.com/ticket/16006#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 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.
