#31287: Rename mark_safe and "safe" template filters to something less safe
sounding
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: nobody
Johnson |
Type: | Status: new
Cleanup/optimization |
Component: Template system | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Claude Paroz):
Meh... You will annoy thousands of devs having to rename multiple
occurrences of those names, with IMHO a very small gain. EIther the
developer is sensible to security coding and she's probably already
careful about those, or the developer doesn't care and just wants to see
its string be shown properly, whatever the name of the function is.
TL;DR I'm not convinced.
--
Ticket URL: <https://code.djangoproject.com/ticket/31287#comment:1>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/068.a2d26bea82a3012d9e8d49f2e32642c5%40djangoproject.com.
