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
13138	"Precedence of ""blank"" model attribute and ""required"" form attribute is unclear"	saxon75@…	nobody	"There appears to be a discrepancy between model/form validation in 1.2 and form validation in 1.1.1.  Previously, a ModelForm field defined in the form subclass with the ""required=False"" option would not throw a ValidationError if the field was submitted blank, regardless of whether or not the model field was defined with ""blank=True."" This appears not to be the case in 1.2--if you submit a blank ModelForm field without the model field being defined with ""blank=True,"" it will still throw a ValidationError even if you have the ModelForm field with ""required=False.""  It's unclear which setting should take precedence when the two conflict (especially in cases where one is set explicitly and the other is left as the default, e.g. required=False in the form and no explicit declaration in the model) and the documentation doesn't appear to note the necessity of explicitly setting both options the same way."		closed	Forms	1.2-beta		fixed			Accepted	0	0	0	0	0	0