#36225: createsuperuser validation breaks if USERNAME_FIELD is distinct but user
manager deliberately lacks get_by_natural_key()
-------------------------------------+-------------------------------------
Reporter: Jonas Dittrich | Owner: Joe
| Babbitt
Type: Bug | Status: closed
Component: contrib.auth | Version: 5.1
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls <jacobtylerwalls@…>):
In [changeset:"865384f96cc588b2babe747d192771ffea07c991" 865384f9]:
{{{#!CommitTicketReference repository=""
revision="865384f96cc588b2babe747d192771ffea07c991"
[6.1.x] Fixed #36225 -- Coped with lack of get_by_natural_key() in
createsuperuser.
Backport of 2c8c0ca0a0b73b167c29db506f810c318f915587 from main.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36225#comment:16>
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019e6fdc40f5-29050409-73c9-450e-8da9-fae06643484d-000000%40eu-central-1.amazonses.com.
