I think being able to specify permissions for the AnonymousUser is useful, but hacking this in as a row in the database for User is not the right approach.
I'm +1 for the ability to give permissions to anonymous users. On Oct 24, 9:59 pm, "Dj Gilcrease" <[EMAIL PROTECTED]> wrote: > On Fri, Oct 24, 2008 at 8:49 PM, James Bennett <[EMAIL PROTECTED]> wrote: > > Seeing as you can already create a special user object in your own app > > and treat it as "the" "anonymous" user, I don't see any benefit from > > this, as I told you when you mentioned this in the #django-dev > > channel. Plus, it's unlikely that everyone who wants a "real" > > anonymous user will have exactly the same needs you do, which makes > > this even more a candidate for being your own code in your own app, > > rather than everyone's code in everyone's copy of Django (this is a > > huge bikeshed argument waiting to happen, in other words). > > I understand that and it is likely what I will end up doing, but I > figured I would throw my proposal and patch up here for people to > debate so I could see what other potential use cases might not be met > by this so that I can try and make my AnonUser model work for as many > people as possible. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
