Open Stack

+1 to everything Russell just said and of course Blueprints for this. One for #3 (changing from mox -> Mock) would be good so that anyone who is bored or finds this urgent can collaborate. Also, we need to make sure reviewers are aware (Hopefully they are reading this).

-Alex

-----Original Message-----
From: "Russell Bryant" <rbryant at redhat.com>
Sent: Wednesday, July 24, 2013 2:45pm
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] Usage of mox through out the Openstack project.

On 07/24/2013 02:32 PM, Kevin L. Mitchell wrote:
> On Wed, 2013-07-24 at 14:12 -0400, Chuck Short wrote:
>> 1. Change mox usage to more python3 friendly such as mock.
>> (https://pypi.python.org/pypi/mock/1.0.1). However this will cause
>> alot of code churn in the projects as we move away from mox to mock.
>>
>>
>> 2. Use the python3 fork called pymox
>> (https://github.com/emonty/pymox). This project has reasonable
>> compatibility with mox and is python3 compatible. Using this option
>> causes less code churn. IMHO this would be the better option.
> 
> My personal preference is that we move to mock; I think it is a better
> methodology, and I like its features.
> 

That's fine with me if everyone feels that way.  I'm afraid it's not a
quick move because of how much we're using mox.  A practical approach
would probably be:

1) Prefer mock for new tests.

2) Use suggestion #2 above to mitigate the Python 3 concern.

3) Convert tests to mock over time, opportunistically, as tests are
being updated anyway.  (Or if someone *really* wants to take this on as
a project ...)

-- 
Russell Bryant

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev