yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #09271
[Bug 1275686] Re: Non-ascii characters not handled correctly
*** This bug is a duplicate of bug 1273301 ***
https://bugs.launchpad.net/bugs/1273301
** This bug has been marked a duplicate of bug 1273301
Unit test failure: Message objects do not support str() because they may contain non-ascii characters. Please use unicode() or translate() instead.
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1275686
Title:
Non-ascii characters not handled correctly
Status in OpenStack Identity (Keystone):
In Progress
Status in OpenStack Neutron (virtual network service):
New
Status in Oslo - a Library of Common OpenStack Code:
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
References