zope.exceptions.exceptionformatter and non-ASCII characters
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zope 3 |
Won't Fix
|
Low
|
Unassigned | ||
zope.exceptions |
Won't Fix
|
Low
|
Unassigned |
Bug Description
I used zope.exceptions
The contract of the exception formatter should explicitly say whether it returns Unicode or not, and various formatting methods should take care to convert the strings as appropriate. I would prefer to get Unicode always.
Source of 8-bit characters: linecache.getline, traceback.
There are some calls to str() and, log.Formatter uses cStringIO -- these would break with Unicode strings.
(Side issue: TextExceptionFo
Changed in zope.exceptions: | |
assignee: | nobody → Marius Gedminas (mgedmin) |
importance: | Undecided → Low |
status: | New → Confirmed |
Changed in zope3: | |
status: | Confirmed → Won't Fix |
Changed in zope3: | |
assignee: | Marius Gedminas (mgedmin) → nobody |
Changed in zope.exceptions: | |
assignee: | Marius Gedminas (mgedmin) → nobody |
Incidentally, there's interesting code in zope.error where it tries to cope with this issue and force everything into ASCII.