Use of str() breaks translation features in OpenStack

Bug #1277301 reported by Luis A. Garcia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
WSME
New
Undecided
Unassigned

Bug Description

For OpenStack to be able to do translation to multiple locales it uses basestrings that don't support becoming str()s because of str()'s lack of ability to have encoding information. Currently wsme is using str() to create a response from an exception's error message here:

https://github.com/stackforge/wsme/blob/0.5b6/wsme/api.py#L215

We can avoid the problem we are currently seeing if we use unicode(e) or six.text_type(e) instead of str(e).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.