#17787: Clear setting-dependant caches when settings are overridden (in tests)
-----------------------------------+--------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Testing framework | Version: 1.4-beta-1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------------------------
Changes (by claudep):
* has_patch: 0 => 1
Comment:
Replying to [comment:12 aaugustin]:
> We're in an inconsistent state right now. Some settings are properly
reset and others aren't;
Let's create tickets for each setting unproperly reset. But auditing the
code to relate settings with global cached variables might be something
hard. I'm afraid only bugs will reveal those.
> the docs still say that the signal isn't used.
>
> We still have to document the new behavior before the next release. At
worst, open django/tests/signals.py, make a list of settings that are
reset, and put that in the docs...
I'm attaching a patch for updating the docs.
--
Ticket URL: <https://code.djangoproject.com/ticket/17787#comment:13>
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 https://groups.google.com/groups/opt_out.
