In this thread. There is a lot of mistaking of an app being installed with Django vs. an app being in the same code repo as Django.
Don't worry people. I don't think anyone is seriously considering throwing away the admin. On Fri, Feb 3, 2012 at 6:55 PM, Joe & Anne Tennies <tenn...@gmail.com>wrote: > I'll throw in my 2 cents. > > Please, please do not remove auth or admin. They really are the selling > point and reason to use Django over something else. That being stated, you > do not have to keep auth or admin in their current forms. I have no problem > whatsoever with making them more of an API than an implementation. > > Figure out the signals an auth backend should have and the basic things > expected to be implemented. For instance, a User should have a user_id, > human-readable name (optional), email address (optional), profile?, > permissions, auth_groups, and backend authenticated with (I'm sure there > may be others that should be here). I think the current signals are > probably fine. Also needed would be some sort of "backend plugin loader" > (like the one for the ORM allowing MySQL, Postgres, etc.) Then include a > very basic implementation that just does username/password authentication > with the database as an app that can be used. (Others can maintain an open > id, facebook, etc. outside the core of Django, but the standard is there.) > PS: Something like Twisted.cred may a good reference for such an abstract > thing. > > Ditto for the admin. So what if it's not ajax or less, just make a simple > one that works and let others extend/reimplement to get a fancy version. > > This to me is congruent with the answer I had heard thrown around for > South. Don't include South in Django, but include a base specification that > South and nashvegas can agree to. (required parts needed in the ORM and > schema revision tracking, etc.) Then include a simple implementation that > can migrate databases via some script but not autodetect changes. > > > Basically, I see a big need for Django to start providing specifications > to how things > -- > Joe & Anne Tennies > tenn...@gmail.com > > -- > 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. > -- 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.
