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 intro
+1
2014-03-11 5:54 GMT+08:00 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 th
On 10 Mar 2014, at 22:54, David Kranz 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
> sense to d
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 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
On 03/13/2014 10:50 AM, Joe Hakim Rahme wrote:
On 10 Mar 2014, at 22:54, David Kranz 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 P
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 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
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 wrote:
There are a number of patches up for review that make various changes
to use "six" apis instead of Python 2 constru
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 rele
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 understan
