#26790: Move BaseUserManager.normalize_email() to AbstractUser
--------------------------------------+------------------------------------
     Reporter:  tam0407               |                    Owner:  tam0407
         Type:  Cleanup/optimization  |                   Status:  assigned
    Component:  contrib.auth          |                  Version:  master
     Severity:  Normal                |               Resolution:
     Keywords:  normalize_email       |             Triage Stage:  Accepted
    Has patch:  0                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------
Changes (by timgraham):

 * version:  1.10 => master
 * stage:  Unreviewed => Accepted


Comment:

 If the user has overridden `BaseUserManager.normalize_email()`, we need to
 use that implementation during the deprecation period. The idea is similar
 to the deprecation of `ModelAdmin.declared_fieldsets` in
 ebb3e50243448545c7314a1932a9067ddca5960b.

 It seems to me the `normalize_email()` should be moved to `AbstractUser`
 (which has the `email` field) rather than `AbstractBaseUser`.

--
Ticket URL: <https://code.djangoproject.com/ticket/26790#comment:2>
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/065.a1a3cc75043d7771e701f204d2bc59ac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to