#29449: UserCreationForm and UserChangeForm don't work if username isn't a
CharField
-------------------------------------+-------------------------------------
Reporter: Sławek Ehlert | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: 2.1
Severity: Release blocker | Resolution:
Keywords: auth forms | Triage Stage: Accepted
UserCreationForm UserChangeForm |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
If a patch isn't forthcoming (the best way to avoid the issue that Markus
pointed out in comment 1 isn't obvious to me), I think we could deescalate
from a release blocker by documenting this limitation.
--
Ticket URL: <https://code.djangoproject.com/ticket/29449#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/063.1dc8f9fabaf69ba78a92b37e1667e2cf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
