Am 25.10.2011 23:22, schrieb Christoph Zwerschke:
Ok, I'll try to work out a full patch with unit tests tomorrow. Just
wanted to know if anybody already stumbled over that problem.
It's here now: https://github.com/Pylons/pyramid_debugtoolbar/pull/43
-- Christoph
--
You received this message
Am 25.10.2011 22:41, schrieb Chris McDonough:
It's hard to tell if what you described is OK without seeing that code
in context; would you mind submitting a pull request with your suggested
fix?
Ok, I'll try to work out a full patch with unit tests tomorrow. Just
wanted to know if anybody alre
On Tue, 2011-10-25 at 22:31 +0200, Christoph Zwerschke wrote:
> My solution was to wrap exceptions and tracebacks in text_() calls, e.g.
> in render_summary, render_full and generate_plaintext_traceback.
>
> This avoids the crashes, but utf-8 messages will look odd because
> text_() assumes lati
The Pyramid debug toolbar is a real blessing. I think we need to rip it
for use with TurboGears, too ;-)
However, I have experienced some issues with exceptions when they have a
non-ascii error message (I remember there were similar problems with the
Pylons weberror module). For instance, Post
