#17725: Extend EMPTY_VALUES for the form and|or model field
-----------------------------+--------------------------------------
Reporter: prudnikov | Owner: nobody
Type: New feature | Status: closed
Component: Forms | Version: 1.3
Severity: Normal | Resolution: wontfix
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 prudnikov):
* cc: v.prudnikov+django@… (added)
Comment:
clean_<field> method is not called if you pass "None" into UrlField or
EmailField.
REmoving error messages from form.errors manually doens't seems a good
solution to me...
{{{
>>> urllib.urlencode({"name":"Hello","parent":"None"}) # my parent
is actually called "None", anything wrong with that?
}}}
If developer has defined string "None" as real None I don't see anything
wrong with that.
I think this feature is quite similar anti-feature as `validators`
attribute because the same way developer can raise an exception when
string "None" has passed for `parent`, anything wrong with that? Well, may
be, but in this case why `validators` is not anti-feature and
`empty_values` is?
I think flexibility is the key.
--
Ticket URL: <https://code.djangoproject.com/ticket/17725#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
