Incorporating changes in swift for py3 compatibility.

[janonymous]

py3 compatibility could be provided by Solving few mentioned issues among many

 *Provide compatibility with python 3 , like Replace it.next() with next(it)

 *Replacing dict.keys() which stores an entire list in memory to dict.iterkeys(). (which does not consume memory by keeping entire list in memory) ==> (furthur these methods might have to be imported from six package.)

*Convert the result of keys(), values() and items() dict method to list
when a list is expected. On Python 3, these methods now return an
iterator, not a list.

I could also register this as a blueprint but i was not sure it would be acceptable so i logged it as a bug/suggestion.
Kindly provide your valuable comments on the same.

[janonymous (janonymous)]

If Confirmed i am happy to contribute for the same. :)

[janonymous (janonymous)]

A Sample of iter.next() -> next(iter) are attached.

[Christian Schwede (cschwede)]

There are already several patches to add py3 support in Swift: https://review.openstack.org/#/q/status:open+project:openstack/swift+branch:master+topic:py3,n,z

Just to make sure work is not done twice :)

[janonymous (janonymous)]

Yes, you are right Christian, but the one i mentioned were not among them , so just mentioned them here . :)

[John Dickinson (notmyname)]

The (currently non-voting) py3 gate job will let us know when this is "done"

[clayg (clay-gerrard)]

This is a huge ongoing effort:

https://review.openstack.org/#/q/project:openstack/swift+branch:master+topic:py3,n,z

I don't think this bug is the best way to track this OpenStack wide goal?