On Mon, Aug 5, 2013 at 10:00 PM, ptone wrote:
> This seems like a reasonable change. I don't love the fact that the
> contrib.auth built in forms quasi support custom user models, as it leads
> to a less clear delineation about what parts of contrib.auth are tightly
> coupled auth the default Use
This seems like a reasonable change. I don't love the fact that the
contrib.auth built in forms quasi support custom user models, as it leads
to a less clear delineation about what parts of contrib.auth are tightly
coupled auth the default User model.
https://docs.djangoproject.com/en/1.5/topic
Hi all,
I have implemented a custom user model that extends AbstractBaseUser, where
an EmailField is set as the USERNAME_FIELD. Logging in with a default auth
login view and AuthenticationForm works nicely, however, the username field
is still a CharField and thus rendered as a regular input field
