On Thu, Apr 5, 2012 at 1:02 PM, Adrian Holovaty <adr...@holovaty.com> wrote:
> 2012/4/5 Ian Lewis <ianmle...@gmail.com>: > > I'm curious though how the admin fits into your ideas. If you wanted to > use the > > admin, would you have to use a User model that has and or supports all > the > > cruft on the current user model? e.g. username, password, email, > permissions > > etc. > > Yes, you'd need to tell the admin how your User model interacted with > it -- how it authenticates, how permissions work, etc. > > Adrian > > -- > 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 > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > I haven't been following this thread nearly closely enough. But ISTM that any abstraction that doesn't let the admin work with any User (assuming it supplies the right interface) isn't very useful, and rather misses the point. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero -- 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 django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
