Hi,
I'm porting OpenStack code to Python 3 for two years. I'm happy with
six. It has been adopted by all OpenStack projects which are being
ported to (or have been ported to) Python 3. It was discussed to use
python-future in Swift, but Swift is now using six too.
I wrote a tool to port an OpenStack project to six:
https://pypi.python.org/pypi/sixer
It does at least half of the port for you. I wrote the tool to be able
to produce patches reviewable by a human: you can easily select which
operations are enabled or not to produce smaller patches, and you can
rerun the tool multiple times.
FYI I wrote an article to explain why I wrote a new tool for OpenStack:
https://haypo.github.io/python3-sixer.html
Victor
Le 25/11/2015 03:33, Eric Kao a écrit :
Hi all,
I’ve been using the python-future library for Python 3 porting and want
to see what people think of it.
http://python-future.org/overview.html#features
The end result is standard Python3 code made compatible with Python2
through library imports. The great thing is that Python 3 execution is
mostly independent of the library, so once Python 2 support is dropped,
the use of the library can be dropped too.
Anyone know why it’s not used in OpenStack perhaps alongside six? Thanks!
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
