yahoo-eng-team team mailing list archive

[Ann Kamyshnikova <akamyshnikova@xxxxxxxxxxxx>]

I've analyzed codebase and came to conclusion that this bug is invalid for Neutron. Places where we have str() conversion around exceptions divide into two categories:
- where stringified exceptions are checked for equiality with or inclusion of literal strings which are of str type in both Python 2.x and 3.x, converting them to unicode will only add one more implicit unicode->str conversion step;
- where exceptions are immediately passed as arguments to string formatting operator, in these cases explicit str() conversion is not needed since %s substitution already does the same conversion.
Both of these cases need no special unicode handling. For the second case I've filed a bug here:https://bugs.launchpad.net/neutron/+bug/1398839

** Changed in: neutron
       Status: Triaged => Invalid

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

Title:
  Handle unicode exception messages

Status in Orchestration API (Heat):
  Fix Released
Status in OpenStack Neutron (virtual network service):
  Invalid
Status in Python client library for Neutron:
  In Progress

Bug description:
  There are many places in the code that explicitly ask for byte code
  strings while using exception messages. They should be able to work
  with unicode string and use it in a way that is PY3 compatible.

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