I think this is an issue that solved itself when we moved to Python 3,
and no fix is needed.
** Changed in: glance
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1210031
Title:
Enforce unicode usage within glance
Status in Glance:
Won't Fix
Bug description:
Glance currently does not enforce unicode usage within itself,
instead, it has a mixed usage of encoded and decoded strings all
around. An example of this, is the fact that exceptions expect a str
whereas other areas are working w/ unicode. This has forced us to
create some workarounds in some cases where more simple str handling
would have been possible if there was a standard.
This whole behavior should be unified and standardized. It's a good
practice to always decode everything and encode it at the very last
moment before going "out there".
NOTE: To the implementer, pls, make use of safe_encode and safe_decode
(openstack/common/strutils.py) when decoding / encoding.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1210031/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
