UnicodeDecodeError: 'ascii' codec can't decode byte 0xa4 in position 26: ordinal not in range(128)

[Tzuchun]

How to Reproduce

While doing a GET operation on /discussion, Trac issued an internal error.

(please provide additional details here)

System Information

Trac	0.11b1
Python	2.5.2 (r252:60911, Feb 21 2008, 13:11:45) [MSC v.1310 32 bit (Intel)]
setuptools	0.6c7
SQLite	3.3.4
pysqlite	2.3.2
Genshi	0.4.4

Python Traceback

Traceback (most recent call last):
  File "C:\Python25\Lib\site-packages\trac\web\main.py", line 398, in _dispatch_request
    dispatcher.dispatch(req)
  File "C:\Python25\Lib\site-packages\trac\web\main.py", line 217, in dispatch
    data, content_type)
  File "C:\Python25\Lib\site-packages\trac\web\chrome.py", line 683, in render_template
    return stream.render(method, doctype=doctype)
  File "C:\Python25\Lib\site-packages\genshi\core.py", line 154, in render
    return encode(generator, method=method, encoding=encoding)
  File "C:\Python25\Lib\site-packages\genshi\output.py", line 45, in encode
    output = u''.join(list(iterator))
  File "C:\Python25\Lib\site-packages\genshi\output.py", line 274, in __call__
    for kind, data, pos in stream:
  File "C

[peter kese]

Seems to be overridden by #7033.

[Jeroen Ruigrok van der Werven]

/discussion is actually the discussion plugin, so this needs to be taken up with those developers. So it is not quite the same as #7033.

[Jeroen Ruigrok van der Werven]

Reflect more correct resolution.

[anonymous]

Execused me, let me describe more details. The Issue 7032 and 7033 are similar situation. This situation happens after I activate the discussion plugin (or even any other newly installed plugins).

Actually, I have tried to installed dozens of plugin in my desktop, but none of them succeeded. Before that, I had successfully installed several trac plugins in my notebook, all of them works fine. The wired thing is all the package I installed both in my desktop and notebook are the same.

[Christian Boos]

/discussion → discussion plugin. Nothing we can do about this. If #7032 and #7033 are caused by the same problem, fine, let's discuss that on #7033.