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
15683	the force_escpe filter should not call mark_safe	Germano Gabbianelli	Marcos Moyano	"in template.defaultfilters.force_escape you are explicitly calling mark_safe on the value returned by utils.html.escape, but escape already calls mark_safe on the string it returns
http://code.djangoproject.com/browser/django/trunk/django/utils/html.py#L30
http://code.djangoproject.com/browser/django/trunk/django/template/defaultfilters.py#L391

I reported this on #django-dev and got answered:
{{{
<carljm> tyrion-mx: indeed, i think the mark_safe in force_escape is unnecessary. though also harmless - it costs exactly one function call and one isinstance check.
}}}"	Cleanup/optimization	closed	Template system	1.3	Normal	fixed	force_escape mark_safe		Accepted	1	0	1	0	0	0