Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is there any performance/architectural cost (or benefit) for defining too many custom tags and filters in Django? I’m still trying to wrap my mind around the fact that virtually any time Django template language doesn’t allow me to do something I can fall back to define my own workaround.
I know this is a very generic question, but I’d be very grateful if you could give me some use cases when over-relying on these tools is either good or bad.
There is a cost, but unless you overuse template tags you should not care.
This is why, by the way, Django widgets’ html templates are defined in python code rather than in templates.
Remember that it doesn’t matter how complicated is your template, in the end, if you use some caching mechanism the template is generated only once in a while..
Myself, I always prefer template tags and filters, even for the smallest things.