#21882: Early modification bug in Django 1.6. with mark_safe + ugettext_lazy
-------------------------------------+-------------------------------------
Reporter: nealtodd | Owner: bmispelon
Type: Bug | Status: assigned
Component: | Version: 1.6
Internationalization | Resolution:
Severity: Release blocker | Triage Stage: Accepted
Keywords: mark_safe | Needs documentation: 0
ugettext_lazy | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by nealtodd):
Hi Baptiste,
Thanks for looking into that (glad it wasn't just my brain melting ;-).
I've tried the `force_text` coercion at the start of the 1.6
implementation of `conditional_escape` (different from the 1.7
implementation) and that's resolving the issues I was seeing. So, thanks
for doing the backport too.
Cheers, Neal
--
Ticket URL: <https://code.djangoproject.com/ticket/21882#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.e32ff7b5af6b7d994d208694e0a4ff78%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
