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 which is obviously a bad thing. What was the reason > for this decision?
It may look like a class attribute, but it's not. LazyUser has overridden __get__, so request.user is a descriptor, not a plain old attibute. It *must* be assigned to the class, and not an instance, or __get__ will not be called. You can google python descriptors for more info. Joseph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers -~----------~----~----~----~------~----~------~--~---
