#29602: Jinja2's forceescape filter doesn't work on Django's safe strings
---------------------------------+--------------------------------------
Reporter: Richard Eames | Owner: nobody
Type: Bug | Status: new
Component: Template system | Version: 2.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Comment (by Richard Eames):
I agree, it is a bit late in the 2.0 life cycle to revert it; a note in
the 2.0 change log would be very helpful for anyone else that's doing a
late upgrade like I was (while upgrading I was checking everything in the
release notes against our code base). I also assume it's too late in the
2.1 release cycle to fix in some way?
As a work around, I should either be able to use django's `force_escape`,
or manually wrap the variable in Jinja's `MarkUp()` function so that it
works with Jinja's `forceescape`.
--
Ticket URL: <https://code.djangoproject.com/ticket/29602#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.6517c67399b1970b16c1e5fa59889915%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
