#15026: Test failures in django.contrib.sessions on default project when
memcached
used as CACHE_BACKEND
----------------------------------------------+-----------------------------
Reporter: jsdalton | Owner: nobody
Status: new | Milestone: 1.3
Component: django.contrib.sessions | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
----------------------------------------------+-----------------------------
Changes (by PaulM):
* needs_better_patch: 0 => 1
* stage: Design decision needed => Accepted
Comment:
Design Decision Needed is the wrong status for this ticket. We agree that
the problem needs to be fixed, the specific way the patch goes about doing
it isn't the subject of debate among core devs. I'm moving this back to
accepted status, since I haven't specifically applied and tested the new
patch yet.
I agree that avoiding `cache.clear()` is the polite thing to do here.
In the proposed patch, is there a reason we aren't doing the delete at the
start of every test run? It's better to write test code that can take the
database from any state (including a previous test that failed somewhere
unusual or odd) than to require our clean up code to run successfully for
the next test run. I'm not familiar enough with the code that this is
testing to know if that's particularly difficult here, but it seems like a
better option.
--
Ticket URL: <http://code.djangoproject.com/ticket/15026#comment:4>
Django <http://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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
