#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 Jon Dufresne):
I was wondering if this fix could be eligible for a backport to 1.11.x. It
fixes a bug in the new features of:
https://docs.djangoproject.com/en/dev/releases/1.11/#forms
> The new CharField.empty_value attribute allows specifying the Python
value to use to represent “empty”.
https://docs.djangoproject.com/en/dev/releases/1.11/#miscellaneous
> In model forms, CharField with null=True now saves NULL for blank values
instead of empty strings.
The [https://docs.djangoproject.com/en/dev/internals/release-process
/#supported-versions documentation] says the following about fixing bugs
in newly introduced features:
> Major functionality bugs in new features of the latest stable release.
--
Ticket URL: <https://code.djangoproject.com/ticket/28555#comment:8>
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.cf25e827e491762ae50729b0d230b583%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
