qutebrowser/tests/unit
Florian Bruhin 9edc5a665e Handle jinja's UndefinedError in jinja.render
We can get UndefinedError when a new function got added to the jinja
env (and gets called from a template) and the user did update the
on-disk templates but not restart qutebrowser yet.

In this case, let's show a special error page to the user and tell them
to do :report in the unlikely case it's actually a bug.

Fixes #1362.
See #1360.
2016-03-26 00:00:06 +01:00
..
browser Check pep257 via flake8. 2016-02-10 19:18:47 +01:00
commands Fix new flake8 lint. 2016-01-22 17:33:58 +01:00
completion Check pep257 via flake8. 2016-02-10 19:18:47 +01:00
config allow {0} in search engine specification strings to allow multiple instances of the search term in the url 2016-03-17 20:38:05 -04:00
javascript tests: Default to raising=True for qtbot. 2016-01-08 09:49:06 +01:00
keyinput Check pep257 via flake8. 2016-02-10 19:18:47 +01:00
mainwindow Force showing of label in test_elided_text 2016-03-15 08:29:33 +01:00
misc Fix lint 2016-03-17 22:10:58 +01:00
scripts Adjust copyright years. 2016-01-04 07:12:39 +01:00
utils Handle jinja's UndefinedError in jinja.render 2016-03-26 00:00:06 +01:00