#28555: Inconsistent empty value for EmailField(blank=True, null=True) due to
strip
after check for empty value
-----------------------------+---------------------------------------------
Reporter: Olav Morken | Owner: Josh Schneier
Type: Bug | Status: closed
Component: Forms | Version: master
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 Tim Graham <timograham@…>):
In [changeset:"1d1a56c59983ae40675aff2c737bdde8f988e5e9" 1d1a56c]:
{{{
#!CommitTicketReference repository=""
revision="1d1a56c59983ae40675aff2c737bdde8f988e5e9"
[1.11.x] Fixed #28555 -- Made CharField convert whitespace-only values to
the empty_value when strip is enabled.
Backport of 48c394a6fc2594891f766293afec8f86d63e1015 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28555#comment:9>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.38dc06e8fb0280b5d0f8c7a09daefd7a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
