#20296: django.utils.safestring.mark_safe forces evaluation of lazy objects
-----------------------------------+------------------------------------
Reporter: Baptiste Mispelon | Owner: nobody
Type: New feature | Status: new
Component: Utilities | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+------------------------------------
Comment (by Tim Graham):
In the steps to reproduce, should `mark_safe()` be inside
`ugettext_lazy()` as in #27803 instead of the other way around? If so,
maybe this is a wontfix, assuming the documentation is clear about proper
usage.
--
Ticket URL: <https://code.djangoproject.com/ticket/20296#comment:10>
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/067.918936d1f72b51744389f4d2056aebea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
