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
28310	form RangeFields should treat (None, None) as Range(None, None) rather than None	Matthew Schinckel	nobody	"When you clean a `RangeField` and pass it in `('', '')`, or `(None, None)`, it falls through to the `MultiValueField` handling, which, when all values are empty, [https://github.com/django/django/blob/a6b5321ce997b899e540bb427cca98cb2b93a106/django/forms/fields.py#L992 treats the cleaned value as empty].

Thus, `FloatRangeField().clean([None, None])` returns `None`, when it really should return `FloatRange(None, None)`.

There is a very large difference between these."	Bug	closed	contrib.postgres	1.11	Normal	needsinfo			Unreviewed	0	0	0	0	0	0