Re: [openstack-dev] [qa] Python 3.3 patches (using six)

2014-03-14 Thread victor stinner
Hi, I'm working for eNovance and we are working on porting OpenStack to Python 3. Status of the port: http://techs.enovance.com/6722/status-of-the-openstack-port-to-python-3-2 https://wiki.openstack.org/wiki/Python3 I understand that it becomes late for Python 3 changes before Icehouse

Re: [openstack-dev] [qa] Python 3.3 patches (using six)

2014-03-14 Thread Sean Dague
On 03/14/2014 04:49 AM, victor stinner wrote: Hi, I'm working for eNovance and we are working on porting OpenStack to Python 3. Status of the port: http://techs.enovance.com/6722/status-of-the-openstack-port-to-python-3-2 https://wiki.openstack.org/wiki/Python3 I understand that

Re: [openstack-dev] [qa] Python 3.3 patches (using six)

2014-03-13 Thread Joe Hakim Rahme
On 10 Mar 2014, at 22:54, David Kranz dkr...@redhat.com wrote: There are a number of patches up for review that make various changes to use six apis instead of Python 2 constructs. While I understand the desire to get a head start on getting Tempest to run in Python 3, I'm not sure it makes

Re: [openstack-dev] [qa] Python 3.3 patches (using six)

2014-03-13 Thread Joe Gordon
On Thu, Mar 13, 2014 at 7:50 AM, Joe Hakim Rahme joe.hakim.ra...@enovance.com wrote: On 10 Mar 2014, at 22:54, David Kranz dkr...@redhat.com wrote: There are a number of patches up for review that make various changes to use six apis instead of Python 2 constructs. While I understand the

Re: [openstack-dev] [qa] Python 3.3 patches (using six)

2014-03-13 Thread David Kranz
On 03/13/2014 10:50 AM, Joe Hakim Rahme wrote: On 10 Mar 2014, at 22:54, David Kranz dkr...@redhat.com wrote: There are a number of patches up for review that make various changes to use six apis instead of Python 2 constructs. While I understand the desire to get a head start on getting

Re: [openstack-dev] [qa] Python 3.3 patches (using six)

2014-03-13 Thread Sean Dague
On 03/13/2014 04:29 PM, David Kranz wrote: On 03/13/2014 10:50 AM, Joe Hakim Rahme wrote: On 10 Mar 2014, at 22:54, David Kranz dkr...@redhat.com wrote: There are a number of patches up for review that make various changes to use six apis instead of Python 2 constructs. While I understand

Re: [openstack-dev] [qa] Python 3.3 patches (using six)

2014-03-13 Thread David Kranz
On 03/13/2014 04:56 PM, Sean Dague wrote: On 03/13/2014 04:29 PM, David Kranz wrote: On 03/13/2014 10:50 AM, Joe Hakim Rahme wrote: On 10 Mar 2014, at 22:54, David Kranz dkr...@redhat.com wrote: There are a number of patches up for review that make various changes to use six apis instead of

Re: [openstack-dev] [qa] Python 3.3 patches (using six)

2014-03-11 Thread li zheming
+1 2014-03-11 5:54 GMT+08:00 David Kranz dkr...@redhat.com: There are a number of patches up for review that make various changes to use six apis instead of Python 2 constructs. While I understand the desire to get a head start on getting Tempest to run in Python 3, I'm not sure it makes

[openstack-dev] [qa] Python 3.3 patches (using six)

2014-03-10 Thread David Kranz
There are a number of patches up for review that make various changes to use six apis instead of Python 2 constructs. While I understand the desire to get a head start on getting Tempest to run in Python 3, I'm not sure it makes sense to do this work piecemeal until we are near ready to