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. My complaint was based on a real bug where all my concurrent requests suddenly had a single shared user instance. > I did a simplified descriptor test and found that the > current code *does* act more or less like a class attribute. I've > created a new ticket with a patch that fixes the problem. The cached > user is currently stored as an attribute of LazyUser, but should be > stored as an attribute of the request. Thanks! This both fixes it and makes a perfect example how descriptors work :-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---
