Modify ↓
#7627 closed defect (duplicate)
UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-6: ordinal not in range(128)
Reported by: | Owned by: | anonymous | |
---|---|---|---|
Priority: | normal | Component: | TagsPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.11 |
Description
How to Reproduce
While doing a GET operation on /tags
, Trac issued an internal error.
The tags included in the WikiPage in Korean. It means is, I can see the error is, If this is the WikiPage name of the page to Korean.
Request parameters:
{'q': u"'lifeguide'"}
User agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.127 Safari/533.4
System Information
Trac | 0.12
|
Genshi | 0.6
|
mod_wsgi | 3.2 (WSGIProcessGroup WSGIApplicationGroup %{GLOBAL})
|
pysqlite | 2.4.1
|
Python | 2.6.5 (r265:79063, Apr 9 2010, 15:16:58) [GCC 4.1.2 20080704 (Red Hat 4.1.2-48)]
|
setuptools | 0.6c11
|
SQLite | 3.3.6
|
jQuery | 1.4.2
|
Enabled Plugins
TracGit | 0.12.0.2dev-r7757
|
TracTags | 0.6
|
Python Traceback
Traceback (most recent call last): File "build/bdist.linux-i686/egg/trac/web/main.py", line 513, in _dispatch_request dispatcher.dispatch(req) File "build/bdist.linux-i686/egg/trac/web/main.py", line 235, in dispatch resp = chosen_handler.process_request(req) File "build/bdist.linux-i686/egg/tractags/web_ui.py", line 99, in process_request data['tag_body'] = macro.expand_macro(formatter, None, query) File "build/bdist.linux-i686/egg/tractags/macros.py", line 80, in expand_macro key=lambda r: str(r[0].id)): File "build/bdist.linux-i686/egg/tractags/macros.py", line 80, in <lambda> key=lambda r: str(r[0].id)): UnicodeEncodeError: 'ascii' codec can't encode characters in position 0-6: ordinal not in range(128)
Attachments (0)
Change History (2)
comment:1 Changed 14 years ago by
Resolution: | → duplicate |
---|---|
Status: | new → closed |
comment:2 Changed 14 years ago by
Component: | SELECT A HACK → TagsPlugin |
---|
Note: See
TracTickets for help on using
tickets.
0.6 version still have this problem. for fixing, please refer #3334