#24046: Consider deprecating the "escape" half of django.utils.safestring
--------------------------------------+------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Cleanup/optimization | 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 timgraham):
I started [https://github.com/django/django/pull/6015 some exploratory
work]. I remove usage of `mark_for_escaping()` and `EscapeData` in the
template engine to give an idea of what the code might look like with them
removed. It wasn't difficult to get the tests passing besides a couple
modifications to tests in `test_force_escape.py` which seem like edge
cases (chained usage of `escape|force_escape`).
Aymeric, I didn't think through the upgrade path completely, but could
elaborate on the difficulties you foresaw in that last comment if you
remember them? Maybe the tests don't capture why this is tricky.
--
Ticket URL: <https://code.djangoproject.com/ticket/24046#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 [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.f58eec24fa59fac562d12cce77b700dd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
