We figured out the phenomenon that triggered this problem:
The djangobb middleware was saving items to the cache using integers
(user ids) as the key and True as the value. Obviously this is an
abhorrent practice in its own right both for disambiguation and
security.
We have submitted a patch (w
Hi,
It sounds like you're looking at tests for
django.contrib.sessions.backends.cached_db. If that is the case, then
it's not unusual that you would end up calling the LocMem cache
backend. The cached_db session backend does all of its reads from the
cache, only falling back to the database sessio
I posted this message on -users today, but at PaulM's urging, I'm
bringing it over here out of concern that it may reflect a bug in the
contrib.sessions test suite.
Here's the original message from -users (some -dev only notes follow) :
I am having a problem with contrib.sessions.tests.test_valid
