>
>
>
>- I believe that we should add an AbstractEmailUser as a subclass of
>AbstractBaseUser, and make AbstractUser subclass it.
> - So, right now we have AbstractBaseUser -> AbstractUser -> User.
> - My desired hierarchy would be:
> - AbstractBaseUser
> -
Hi Luke -
I just wanted to clarify the approach I'm using - The issue of whether or
not the EmailUser is in contrib.auth or in a new app contrib.auth_email is
a separate issue from code duplication. Either way, you'd have to create
new versions of UserCreationForm, UserChangeForm, UserAdmin, and
Hi all - I updated Russ's new wiki page to include the work I've done so
far: https://code.djangoproject.com/wiki/ContribEmailAuth Again, the patch
I've been working on is here:
https://github.com/tanderegg/django/tree/ticket_20824_master Please let me
know if you have any feedback.
The only
