id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
4051	[] not in EMPTY_VALUES in forms	webograph <webograph@…>	mdnesvold	"the {{{EMPTY_VALUES}}} list of newforms, which is used to test emptyness of required fields, lists {{{''}}} and {{{None}}}, but not {{{[]}}}, which is counter-intuitive for list-like fields and requires those to implement their own emptyness check instead of relying of their parent class's checks. an example of this is the {{{MultipleChoiceField}}} (source:django/trunk/django/newforms/fields.py line 376).

this could potentially be fixed by checking {{{bool}}}ean {{{True}}}ness instead of comparing to a list of known false values, although we would have to solve the problem of {{{int(0)}}} and {{{float(0)}}}, which are {{{bool}}}ean {{{False}}} but not considered omitted in most cases, by catching it in a separate {{{NONEMPTY_VALUES=[0]}}}, which would diminish the elegancy of that solution.

(References: <461FD3E4.8040109@eml.cc> in the django-development list)"	Bug	closed	Forms	1.0	Normal	fixed			Accepted	1	0	1	1	0	0