Pyramid Debug Toolbar: Issue #44

47 views
Skip to first unread message

Simon Yarde

unread,
Nov 14, 2011, 5:02:29 AM11/14/11
to pylons-...@googlegroups.com
Hi All

Does anyone have any information on progress for Pyramid Debug Toolbar issue #44?

The issue causes the exception below when URI's contain accented characters (in my case 'ü'). Pyramid behaves normally without error when debug toolbar is turned off.

A temporary patch/workaround would be really useful, other than turn off debugging :)

We have a huge product database and many of the brand/product names contain accented european characters, so the issue is causing a few embarrassments after the big-sell to get Pyramid adopted!

Exception:
...
> headers.jinja2", line 13, in top-level template code
> <td>{{ value|escape }}</td>
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 13:
> ordinal not in range(128)

Caused by: accented characters in URI

Open issue:
https://github.com/Pylons/pyramid_debugtoolbar/issues/44

.. and possibly this one related:
https://github.com/Pylons/pyramid_debugtoolbar/issues/9


Best, Simon

Christoph Zwerschke

unread,
Nov 14, 2011, 5:39:56 AM11/14/11
to pylons-...@googlegroups.com
Am 14.11.2011 11:02, schrieb Simon Yarde:
> A temporary patch/workaround would be really useful, other than turn off debugging :)

Here is a patch for this issue, let us know how it works:
https://github.com/Pylons/pyramid_debugtoolbar/pull/43

-- Christoph


Simon Yarde

unread,
Nov 14, 2011, 6:34:13 AM11/14/11
to pylons-...@googlegroups.com
Thanks for your reply :)

This may be a big ask... but could you briefly outline the steps I would need to take to download pyramid debug toolbar from github and apply the patch; and following this how I would update it for future tagged releases?

I'm very happy to read any documentation. Previously I've only used git for day-to-day versioning of my own projects - an understanding of the overall process I'm aiming for here would really help confidence and perhaps allow me (and others out there) to maintain their pyramid packages better.

At the moment I have pyramid_debugtoolbar 0.9.4 installed via pip.

Happy to report to this thread (and/or github tracking) how I get on with debugtoolbar and jinja2 with i18n requirements.

All the best, Simon


At the moment, I have Pyramid 1.2.1 installed via pip.

> --
> You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
> To post to this group, send email to pylons-...@googlegroups.com.
> To unsubscribe from this group, send email to pylons-discus...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
>

Blaise Laflamme

unread,
Nov 14, 2011, 10:10:46 AM11/14/11
to pylons-...@googlegroups.com
Do easy_install -U pyramid_debugtoolbar, latest version is 0.9.5 and templates are now mako based.

Christoph Zwerschke

unread,
Nov 14, 2011, 11:06:10 AM11/14/11
to pylons-...@googlegroups.com
Am 14.11.2011 12:34, schrieb Simon Yarde:
> This may be a big ask... but could you briefly outline the steps I
> would need to take to download pyramid debug toolbar from github and
> apply the patch; and following this how I would update it for future
> tagged releases?

Well, the easiest way is to get my fork which includes the patch at
https://github.com/Cito/pyramid_debugtoolbar - simply click on the "ZIP"
button, unpack the zip file and run "python setup.py".

Or, you clone the original and then pull my changeset with "git pull
https://github.com/Cito/pyramid_debugtoolbar".

Concerning updates, I just hope it will be fixed this way or another in
the official branch soon.

-- Christoph

Reply all
Reply to author
Forward
0 new messages