should remove the use of str() with LOG.* and exceptions in Cinder
Bug #1274245 reported by
Jay Bryant
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
Jay Bryant |
Bug Description
It is my understanding that the use of str() is now frowned upon and that six.text_type should be used instead as we move forward to Python3 . There are many instances where str() is being used in Cinder that it appears need to be addressed.
Changed in cinder: | |
assignee: | nobody → Jay Bryant (jsbryant) |
Changed in cinder: | |
importance: | Undecided → High |
summary: |
- should remove the use of str() in Cinder + should remove the use of str() with LOG.* and exceptions in Cinder |
Changed in cinder: | |
milestone: | none → icehouse-3 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | icehouse-3 → 2014.1 |
To post a comment you must log in.
Some background. I came across this concern as I am trying to re-enable lazy translation for Cinder. I was referred to this bug as a reason why we probably shouldn't be using str() for anything logging or exceptions: https:/ /bugs.launchpad .net/oslo/ +bug/1225099 .
Open to discussion as to thoughts on whether this is an appropriate change.