python - Why is the stack trace when using Jinja2 templates with Django not as specific as with the default Django template engine? -


i have installed latest version of django-jinja plugin , followed instructions templates processed jinja instead of defulat django templating language on fresh install of django 1.11.

the first thing noticed stack traces appear when there error unspecific compared dtl templates, , compared flask projects (that default jinja). default template engines, stack trace short , sweet , pinpoints right error happened, mentioning file name , line number. jinja templates in django, can dig usable information out of several lines spits out running through couple dozen functions of installed packages, time consuming pick through , decipher.

is there prevents jinja override having ability interpret stack trace 'human friendly' django/flask default engines? fix this?


Comments

Popular posts from this blog

php - Permission denied. Laravel linux server -

google bigquery - Delta between query execution time and Java query call to finish -

python - Pandas two dataframes multiplication? -