Bangs his head against the wall.
Yes. Yes, I did. I thought I'd rolled back past that but looks like I
hadn't. How annoying.. I can even see what it's doing and why it's not
working (doesn't exactly explain why using memcache as a backend works, but
hey, I'm happy if it builds :)
Thanks for notic
On Tue, Sep 29, 2009 at 11:30 AM, Oli Warner wrote:
> As this clearly had something to do with the session, I just changed the
> SESSION_ENGINE to file. Different error, but for the same reason, I think:
>
> Traceback (most recent call last):
>
> [snip]session_file = open(self._key_to_file(),
Hr. Just changed the SESSION_ENGINE to .cache (using memcache) and it
works.
No idea what's different about the way it handles session ids that differs
from the others...
I should add that I'm on Ubuntu Karmic (in development) so it's possible
that I've got a newer version of something or oth
As this clearly had something to do with the session, I just changed the
SESSION_ENGINE to file. Different error, but for the same reason, I think:
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.6/django/core/servers/basehttp.py",
line 279, in run
self.result = applica
I've been building a site for a couple of months, on and off. Today when I
log in, everything blows up. The core part appears to come from calling
request.user. That trickles through the database (I assume to get the actual
user object) and detonates with a *InterfaceError: Error binding parameter
5 matches
Mail list logo
