e.message is deprecated in Python3

Bug #1607142 reported by Aimee Ukasick
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
congress
Fix Released
Undecided
Aimee Ukasick

Bug Description

we noticed that we're using 'e.message' in a bunch of places, where e is an exception. That works in Python2 but not Python3. We should be using 'str(e)' instead.

Aimee Ukasick (aimeeu)
Changed in congress:
assignee: nobody → Aimee Ukasick (aimeeu)
Eric K (ekcs)
Changed in congress:
status: New → Triaged
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to congress (master)

Fix proposed to branch: master
Review: https://review.openstack.org/354167

Changed in congress:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to congress (master)

Reviewed: https://review.openstack.org/354167
Committed: https://git.openstack.org/cgit/openstack/congress/commit/?id=6f60b0f8c91db7e2663ff560e5a0d58c4c09ca54
Submitter: Jenkins
Branch: master

commit 6f60b0f8c91db7e2663ff560e5a0d58c4c09ca54
Author: aimee.ukasick <email address hidden>
Date: Thu Aug 11 10:27:51 2016 -0500

    Replaced e.message with str(e)

    For logging the exception message: e.message has been
    deprecated. The preferred way is to call str(e).

    Change-Id: I9520ecafff844fbc09bdc80d564f40e3d59dee60
    Closes-Bug: #1607142

Changed in congress:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/congress 4.0.0.0b3

This issue was fixed in the openstack/congress 4.0.0.0b3 development milestone.

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.