You have commented out the test_raise call so of course this "works", if you can call "printing a report" as "working", which is absolutely not what this bug thread is about.
The problem exposed here is not that the exception i *intentionally* introduced was preventing the report from printing; it is that after a werkzeug upgrade to a version > 0.9, said exception does not appear but instead leads to a client error.
Huh? ...
You have commented out the test_raise call so of course this "works", if you can call "printing a report" as "working", which is absolutely not what this bug thread is about.
The problem exposed here is not that the exception i *intentionally* introduced was preventing the report from printing; it is that after a werkzeug upgrade to a version > 0.9, said exception does not appear but instead leads to a client error.