#20086: UserCreationForm does not support custom models.
------------------------------+--------------------------------------
     Reporter:  efrinut@…     |                    Owner:  nobody
         Type:  Bug           |                   Status:  closed
    Component:  contrib.auth  |                  Version:  1.5
     Severity:  Normal        |               Resolution:  invalid
     Keywords:                |             Triage Stage:  Unreviewed
    Has patch:  0             |      Needs documentation:  0
  Needs tests:  0             |  Patch needs improvement:  0
Easy pickings:  0             |                    UI/UX:  0
------------------------------+--------------------------------------
Changes (by russellm):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 I completely agree that this is desirable in theory. My problem is that I
 simply don't see how it is possible in practice.

 The contract for AbstractAuthUser is that the User has a unique
 identifying field. We have no prior knowledge whether it is a char field,
 and email field, or even an integer field. If it's a char field, we don't
 know if it has any length or other validation constraints. And we don't
 know if there are any other fields on the user model that are needed for
 authentication purposes (for example, you may use a domain and a username
 as a pair for login purposes). And that's when you're only dealing with
 the *username* field. It doesn't deal with any of the other fields that
 UserCreationForm or UserChangeForm needs to deal with.

 So, I'm closing this again. However, it's clearly an issue that people
 aren't happy with, so if you want to pursue this, please take it to
 Django-dev.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/20086#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.c0b9834bbfe094fcb01e1ea927021d48%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to