Enforce unicode usage within glance

Bug #1210031 reported by Flavio Percoco
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
Won't Fix
Low
Unassigned

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.

Changed in glance:
importance: Undecided → Low
description: updated
Feilong Wang (flwang)
Changed in glance:
status: New → Confirmed
Changed in glance:
assignee: nobody → jelly (coding1314)
Revision history for this message
Kuo-tung Kao (jelly) (coding1314) wrote :

If I want to fix the bug, do I need to find out all the string used by glance ?

Changed in glance:
assignee: jelly (coding1314) → nobody
Changed in glance:
assignee: nobody → Victoria Martinez de la Cruz (vkmc)
Revision history for this message
Victoria Martinez de la Cruz (vkmc) wrote :

Is this bug still valid?

Changed in glance:
assignee: Victoria Martinez de la Cruz (vkmc) → nobody
Revision history for this message
Cyril Roelandt (cyril-roelandt) wrote :

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
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.