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
24252	reverse_lazy representation	Stanislas Guerra	nobody	"Hi devs,

This is related to #18776 and #24097 I guess.

Since Django-1.8:

{{{
my_url = ""%s?%s"" % (reverse_lazy(""foo:bar""), params)
}}}

Gives something like:


{{{
""<django.utils.functional.__proxy__ object at 0x103563850>?param1=val1&param2=val2""
}}}



Prior to 1.8, you'd get a ""valid"" result.

A workaround is to force the evaluation with an explicit `unicode(my_lazy_expression)` call. 

Is it a bug?
If not, is it worth a note in the release notes?"	Bug	closed	Core (URLs)	1.8alpha1	Normal	fixed	reverse_lazy	tomas.ehrlich@…	Ready for checkin	1	0	0	0	0	0