#17787: Clear setting-dependant caches when settings are overridden (in tests)
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Testing | Version: 1.4-beta-1
framework | Keywords:
Severity: Release | Has patch: 0
blocker | Needs tests: 0
Triage Stage: Design | Easy pickings: 0
decision needed |
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
r16237 introduced a `setting_changed` signal, triggered by the
`override_settings` decorator / context manager.
However, Django doesn't use this signal to reset caches that depend on
built-in settings. In the current state of thing, the signal is only
usable is third-party code.
Is this a design choice or a bug?
Marking as release blocker since it's a major bug in a new feature.
--
Ticket URL: <https://code.djangoproject.com/ticket/17787>
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.
