yahoo-eng-team team mailing list archive

[Tim Burke <tim@xxxxxxxxxxxxxx>]

Closing for Swift. We've cleaned up our use of xrange (see bug 1262147),
but I think to run down all the places that we expect/require the result
to be a list, we'll need to actually have python3 support (see bug
1691075 and bug 1667579).

** Changed in: swift
       Status: In Progress => Invalid

** Changed in: swift
     Assignee: lizheming (lizheming-li) => (unassigned)

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

Title:
  range method is not same in py3.x and py2.x

Status in Ceilometer:
  Fix Released
Status in Cinder:
  Fix Released
Status in Glance:
  Fix Released
Status in heat:
  Fix Released
Status in OpenStack Identity (keystone):
  Invalid
Status in kolla:
  Fix Released
Status in neutron:
  Fix Released
Status in python-ceilometerclient:
  Fix Released
Status in python-neutronclient:
  Invalid
Status in python-swiftclient:
  Fix Released
Status in OpenStack Object Storage (swift):
  Invalid

Bug description:
  in py3.x,range is xrange in py2.x.
  in py3.x, if you want get a list,you must use:
  list(range(value))

  I review the code, find that many codes use range for  loop, if used py3.x environment,
  it will occure error.
  so we must modify this issue.

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