I think that an easy way to define your own user model is better idea. Auth app should be more generic. It should define a protocol for user, group and permission objects (and of course there should be back compatible implementation of this protocols used by default). There is a ticket about extending auth app: http://code.djangoproject.com/ticket/3011, but I think this could be done in a better way.
Sorry for my english :-) 2010/2/10 Harro <hvdkl...@gmail.com> > Good suggestions, I think removing username and email from the user > might be a good idea. > Right now I authenticate with the email address stored on the profile > and the username is a random hash :) > > As for breaking data and migrations; it shouldn't be that hard to > write a management command that does this. > > > On Feb 9, 5:54 pm, Vitaly Babiy <vbabi...@gmail.com> wrote: > > Vitaly Babiy > > > > On Tue, Feb 9, 2010 at 3:16 AM, James Bennett <ubernost...@gmail.com> > wrote: > > > On Tue, Feb 9, 2010 at 2:09 AM, Harro <hvdkl...@gmail.com> wrote: > > > > - Make email unique and username non-required on the model. That > would > > > > make implementing something that authenticated by email a lot > > > > easier :) > > > > > 1. It's *extremely* unlikely that changes will be considered which > > > require every Django install on the planet to undergo a DB schema > > > migration. > > > > James this is true. Another reason it would be nice to have a > > migration framework for Django. > > > > > > > > > > > > > 2. The appropriate time to discuss possible 1.3 features is when the > > > feature-discussion window for 1.3 comes up. That will happen sometime > > > in April, probably. Suggestions made now are likely to be forgotten by > > > the time that happens. > > > > > Yeah I plan to bring this up again, around that time frame. > > > > > -- > > > "Bureaucrat Conrad, you are technically correct -- the best kind of > > > correct." > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Django developers" group. > > > To post to this group, send email to > django-develop...@googlegroups.com. > > > To unsubscribe from this group, send email to > > > django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@googlegroups.com><django-developers%2Bunsubscr > i...@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-develop...@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com<django-developers%2bunsubscr...@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-develop...@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.
