#36140: UserCreationForm doesn't allow empty password even if password fields
are
specified as "not required"
-------------------------------------+-------------------------------------
Reporter: buffgecko12 | Owner: (none)
Type: Bug | Status: new
Component: contrib.auth | Version: 5.1
Severity: Release blocker | Resolution:
Keywords: form | Triage Stage: Accepted
usercreationform validation |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Natalia Bidart):
Replying to [comment:4 buffgecko12]:
> Thank you. Is there a timeline for when this bug needs to be fixed and
a PR submitted? Just to gauge if I am able to take this on or not.
As Antoliny says, this is a release blocker so we should have a solution
ready by next week, when we have planned the next patch release for Django
5.1.
It's completely fine if you don't have time, me or someone else would grab
this since it's a priority to get solved. Let me know so I start working
on this!
--
Ticket URL: <https://code.djangoproject.com/ticket/36140#comment:10>
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/01070194b1ecafb7-96e1ee2f-d3e1-4aa6-b563-6baf4823d3b3-000000%40eu-central-1.amazonses.com.
