#23746: Allow assertNumQueries to clear caches before it runs
-----------------------------------+------------------------------------
Reporter: wrwrwr | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by wrwrwr):
Just one more note on this one, recently I've came across #11505 (there
are also some discussions on the subject:
[https://groups.google.com/forum/#!topic/django-users/OOGO-3MIO_c 7/09],
[https://groups.google.com/forum/#!topic/django-
developers/zlaPsP13dUY/discussion 7/11],
[https://groups.google.com/forum/#!msg/django-
developers/Ex7X2oFAHoc/TTma3dJU1ccJ 10/11]). This ticket could be replaced
by generalizing the cache clearing / restoring to include site / content
type caches and possibly some of the lru_caches.
--
Ticket URL: <https://code.djangoproject.com/ticket/23746#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/064.aecd93812bf88fad3f75d26d9a097f5d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
