#28050: TemplateSyntaxError should contain template name
-------------------------------------+-------------------------------------
Reporter: Petr Dlouhý | Owner: Roger
| Masse
Type: New feature | Status: assigned
Component: Template system | Version: 1.11
Severity: Normal | Resolution:
Keywords: TemplateSyntaxError | Triage Stage: Accepted
template |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Himanshu Chauhan):
I think that in case of Template Syntax Error it is very unhelpful to show
the python traceback because that will be usually same for all the errors
of this kind and as mentioned in the ticket does not show the template
file path where the error has been encountered. So my solution is to catch
the template syntax error exception and instead of going for default
python exception handling mechanism, we actually display the template
path, template line number and the exception message which I believe will
be more useful than the default python traceback in debugging template
errors.
I would like to work on this and want to know your views about my
approach.
--
Ticket URL: <https://code.djangoproject.com/ticket/28050#comment:13>
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/068.ee25b223f2c2b2f2de590834176af435%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
