#22412: Clarify expectation around template filters and exceptions
--------------------------------------+------------------------------------
Reporter: carljm | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.6
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 carljm):
Right. I guess I don't see template tags/filters as different from any
other code in a Django project in this respect. Lots of Django code, not
just template tags/filters, might get data from users, and any code that
might get data from an external source needs to be careful in how it
handles that data. I think "handle exceptions you are expecting and know
how to handle, and let anything else bubble up" is the correct advice for
all code; the specifics of what that means will vary for different
situations.
--
Ticket URL: <https://code.djangoproject.com/ticket/22412#comment:2>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.f556e9efc09a78ff4908dd7b548150e5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
