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
32134	Upgrading 2.2>3.0 causes named tuples used as arguments to __range to error.	Gordon Wrigley	Adam Johnson	"I noticed this while upgrading a project from 2.2 to 3.0.

This project passes named 2-tuples as arguments to __range queryset filters. This works fine on 2.2. On 3.0 it causes the following error: `TypeError: __new__() missing 1 required positional argument: 'far'`.

This happens because django.db.models.sql.query.Query.resolve_lookup_value goes into the tuple elements to resolve lookups and then attempts to reconstitute the tuple with the resolved elements.
When it attempts to construct the new tuple it preserves the type (the named tuple) but it passes a iterator to it's constructor.
NamedTuples don't have the code path for copying an iterator, and so it errors on insufficient arguments.

The fix is to * expand the contents of the iterator into the constructor.

"	Bug	closed	Database layer (models, ORM)	3.0	Normal	fixed		Adam Johnson	Ready for checkin	1	0	0	0	0	0