#21882: Early modification bug in Django 1.6. with mark_safe + ugettext_lazy
-------------------------------------+-------------------------------------
Reporter: nealtodd | Owner: bmispelon
Type: Bug | Status: closed
Component: | Version: 1.6
Internationalization | Resolution: fixed
Severity: Release blocker | Triage Stage: Accepted
Keywords: mark_safe | Needs documentation: 0
ugettext_lazy | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by bmispelon):
* status: assigned => closed
* resolution: => fixed
Comment:
As noted by the comment above, the regression was fixed by reverting the
commit that introduced it.
I also backported the fix to the 1.6.x branch so it will be part of the
upcoming 1.6.2 release.
Note that using lazy objects with `mark_safe` doesn't really work since
`mark_safe` will force their evaluation (this is what #20296 was trying to
fix).
--
Ticket URL: <https://code.djangoproject.com/ticket/21882#comment:7>
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.50d29d1c7ce8af918ba4fc3fd5e61566%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
