#32396: UsernameField normalisation throws TypeError if the username is empty
------------------------------+--------------------------------------
Reporter: Łukasz Rzepa | Owner: (none)
Type: Bug | Status: closed
Component: contrib.auth | Version: 3.1
Severity: Normal | Resolution: duplicate
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 Carlton Gibson):
* status: new => closed
* resolution: => duplicate
Comment:
Hi, thanks for the report — nice and clear.
I'm going to close this as a duplicate of #31972. As per the docs on
[https://docs.djangoproject.com/en/3.1/topics/auth/customizing/#custom-
users-and-the-built-in-auth-forms Custom users and the built-in auth
forms] you'll need to extend or customise the forms here. (Using
[https://docs.djangoproject.com/en/3.1/ref/contrib/admin/#django.contrib.admin.ModelAdmin.get_form
`ModelAdmin.get_form()`] I imagine.)
--
Ticket URL: <https://code.djangoproject.com/ticket/32396#comment:3>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/062.89db7e28e7ec2b67bdf7ee2c56acacbc%40djangoproject.com.
