Please remove the catch-all try/except in template rendering

[richard at commonground com au]

If a call from a template fails, I want to see it!

Currently, if I have {{ some_function_call }} in a template, and the call raises an exception, I won't have any information about why it failed. Nothing in the browser, the page source or the server log.

[hugo]

You really should provide more specific samples when you don't see a traceback in your debug output, because I definitely know that the system does show tracebacks when exceptions arise. Those tracebacks sometimes might not be perfect in showing what happens (you may need to disable or enable TEMPLATE_DEBUG, because the template debugging code might mask out other stuff sometimes), but you usually do get a traceback.

So some samples might be in order so we know where there might be a problem. Of course the best thing would be a reduced test case we can add to the unittests :-)

[Russell Keith-Magee]

How is this not a duplicate of #1236 (which you submitted yesterday, and I have asked you about)?

May I suggest a quick read through of ​How to ask Smart Questions. In order to verify, fix, and prevent a bug we need a repeatable, standalone test case, or at the very least a comprehensive set of step by step instructions of how to reproduce the problem.

[Jacob]

Duplicate of #1236