#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 | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
Since any data that isn't explicitly marked as safe must be treated as
unsafe, I don't understand why we have `EscapeData` and its subclasses nor
the `mark_for_escaping` function.
It seems to me that we could keep only the "safe" half of
django.utils.safestring and deprecate the "escape" half.
As a matter of fact the "escape" isn't used meaningfully anywhere in
Django.
--
Ticket URL: <https://code.djangoproject.com/ticket/24046>
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/052.458aa41efca114f25026bf888d13e3d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
