← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1275686] [NEW] Non-ascii characters does not handled correctly.

 

Public bug reported:

We need to handle exception messages with `gettextutils` tools instead of using string message as is. Because every message can contain non-ascii characters and it can cause the unicode error:
"UnicodeError: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead."

** Affects: keystone
     Importance: Undecided
     Assignee: Ilya Pekelny (i159)
         Status: In Progress

** Changed in: keystone
     Assignee: (unassigned) => Ilya Pekelny (i159)

** Changed in: keystone
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1275686

Title:
  Non-ascii characters does not handled correctly.

Status in OpenStack Identity (Keystone):
  In Progress

Bug description:
  We need to handle exception messages with `gettextutils` tools instead of using string message as is. Because every message can contain non-ascii characters and it can cause the unicode error:
  "UnicodeError: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead."

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1275686/+subscriptions


Follow ups

References