#32568: Prefer SafeString to mark_safe where possible
-------------------------------------+-------------------------------------
Reporter: Tim McCurrach | Owner: Pravin
Type: | Status: closed
Cleanup/optimization |
Component: Template system | Version: dev
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls <jacobtylerwalls@…>):
* resolution: => fixed
* status: assigned => closed
Comment:
In [changeset:"4774adfaa18391854bb5449b4bcb0e9ab5e66b73" 4774adfa]:
{{{#!CommitTicketReference repository=""
revision="4774adfaa18391854bb5449b4bcb0e9ab5e66b73"
Fixed #32568 -- Replaced mark_safe() with SafeString for literal values.
Replaced instances of mark_safe('some string literal') with
SafeString to avoid the overhead of managing lazy objects.
Thanks Tim McCurrach for the idea and David Smith and Jacob Walls
for reviews.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32568#comment:20>
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 view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019b2d4f3283-777cec65-2f6b-4245-96f7-949dc3db04b0-000000%40eu-central-1.amazonses.com.
