On Wed, Sep 2, 2015 at 10:29 PM, Tim Graham wrote:
> Russ tried to complete the "EmailUser" solution for 1.7, but if I remember
> correctly, there was some issue with testing that couldn't be easily
> resolved.
>
> https://github.com/django/django/compare/master...freakboy3742:emailauth
The issue
Russ tried to complete the "EmailUser" solution for 1.7, but if I remember
correctly, there was some issue with testing that couldn't be easily
resolved.
https://github.com/django/django/compare/master...freakboy3742:emailauth
Anyway, if that issue is still blocked, it looks like the `SimpleIde
I'm +1 on this.
On Sep 2, 2015 10:31 AM, "'Hugo Osvaldo Barrera' via Django developers
(Contributions to Django itself)"
wrote:
> Hi,
>
> I've worked on several apps where users don't have a username, and
> instead require a unique email. Every time, I've used a similar custom
> user model which
Hi,
I've worked on several apps where users don't have a username, and
instead require a unique email. Every time, I've used a similar custom
user model which extended AbstractBaseUser, PermissionsMixin. I then had
to copy-paste several fields from AbstractUser into my custom user
(either because
