Really what you are proposing is an extension of the scope #19353, and I do
feel that if the built in forms are to be made more usable with custom
users, then both the hardcoding of auth.User and the username field should
be addressed together.
One thing not addressed in your authtools
> The current code assumes that if you write a custom model, you'll also
write the corresponding custom forms.
Right. This is what I am proposing be fixed.
On Mon, Jun 3, 2013 at 12:31 PM, Aymeric Augustin <
aymeric.augus...@polytechnique.org> wrote:
> On 3 juin 2013, at 20:01,
On 3 juin 2013, at 20:01, gavinw...@gmail.com wrote:
> Some of the built-in auth forms only work on user models whose
> `USERNAME_FIELD` is `username`.
Hi Gavin,
The current code assumes that if you write a custom model, you'll also write
the corresponding custom forms.
You may want to have
Some of the built-in auth forms only work on user models whose
`USERNAME_FIELD` is `username`. It is possible to remove this constraint
and allow them work on any user model. [django-authtools][1] demonstrates
this possibility.
The two forms in question are `UserCreationForm` and
