#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: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
----------------------------------------------+-----------------------------
Changes (by jsdalton):
* has_patch: 0 => 1
* stage: Ready for checkin => Design decision needed
Comment:
Actually, I thought about it a bit more this a.m. It occurred to me that
calling cache.clear() will clear the entire cache, not just the keys set
during the test run: "Be careful with this; clear() will remove everything
from the cache, not just the keys set by your application."
I've submitted what I think is a better approach, which is just to ensure
that both of the session records created specifically during
`test_invalid_key` are deleted. I wrapped the code in a try/finally block
since an AssertionError might prevent those records from being deleted.
I flipped this back to "Design decision needed" just to ensure a committer
reviewed this slightly different approach, rather than assuming the new
patch was ready for checkin.
--
Ticket URL: <http://code.djangoproject.com/ticket/15026#comment:3>
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.
