Re: Why request.user is a class attribute

2006-09-11 Thread Ivan Sagalaev
Joseph Kocherhans wrote: > Hmm... looking into this more, Ivan was right... kind of (and maybe > this is what he meant, but it's not how I read it, sorry if I > misunderstood). Or it's rather me being a bit sloppy explaining... I saw the __get__ thing but I know how it works only theoretically.

Re: Re: Why request.user is a class attribute

2006-09-11 Thread Joseph Kocherhans
On 9/11/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote: > On 9/11/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > > > > I've just found out that request.user is an attribute of request's class > > not of an instance. Which means that in the environment with multiple > > requests (threaded or not)

Re: Why request.user is a class attribute

2006-09-11 Thread Joseph Kocherhans
On 9/11/06, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > > I've just found out that request.user is an attribute of request's class > not of an instance. Which means that in the environment with multiple > requests (threaded or not) every request.user always points to a single > LazyUser instance wh

Why request.user is a class attribute

2006-09-11 Thread Ivan Sagalaev
I've just found out that request.user is an attribute of request's class not of an instance. Which means that in the environment with multiple requests (threaded or not) every request.user always points to a single LazyUser instance which is obviously a bad thing. What was the reason for this