Hey,
Applying that patch does seem to have helped on the first server;
it's a probabilistic problem, but at least we haven't seen it since
trying this.
The first server was running Debian Etch; the second was running
Gentoo. Both were using Django as installed from their local repo's
(based on 0.95), not directly from SVN. Out of curiosity, is there a
way to determine the version of Django that a package uses, if it
doesn't contain .svn files?
Thanks,
Adam
On Jan 17, 2007, at 11:43 AM, James Bennett wrote:
>
> On 1/17/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
>> Assuming the server is sane, the session cookie is the only thing
>> determining the request.user, so I suspect either your server isn't
>> sane (as in, threading is killing you), or something is wrong with
>> downstream caches.
>
> Or he's using a version of Django prior to revision 3754, which fixed
> a subtle bug in the way request.user is set up. Applying this diff
> should clear up the problem:
>
> http://code.djangoproject.com/changeset/3754
>
> --
> "May the forces of evil become confused on the way to your house."
> -- George Carlin
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" 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-users?hl=en
-~----------~----~----~----~------~----~------~--~---
