Based on an intial run of the Hyper-V Nova tests with pymox
(https://github.com/emonty/pymox), only 2 of the tests required some minor
adjustements while the rest was running perfectly fine by just replacing the
mox import line.
If we plan to support pymox in Havana, I'd be happy to send a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/26/2013 05:35 AM, Roman Bogorodskiy wrote:
Alex Meade wrote:
+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
On Jul 26, 2013 5:53 AM, Russell Bryant rbry...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/26/2013 05:35 AM, Roman Bogorodskiy wrote:
Alex Meade wrote:
+1 to everything Russell just said and of course Blueprints for
this. One for #3 (changing from mox -
On Jul 25, 2013, at 4:01 AM, Julien Danjou jul...@danjou.info wrote:
On Wed, Jul 24 2013, Russell Bryant wrote:
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,
On Thu, Jul 25 2013, Mark McClain wrote:
The Neutron project has been enforcing this approach for about a year now.
We're down to 8 files that still rely on Mox.
Awesome, we'll have to bring Python 3 badges at the next summit for
Neutron devs. ;)
--
Julien Danjou
/* Free Software hacker *
Hi,
The use of mox (https://pypi.python.org/pypi/mox/0.5.3) across the test
suites in the Openstack project is quite extensive. This is probably due to
the fact that it is the most familiar mocking object framework for most
python developers.
However there is big drawback with using mox across
I think moving towards mock is a better long term strategy:
a) I don't you're correct that it's the most familiar for most python
developers. By PyPi installs (A TERRIBLE METRIC, but it's all we have).
Mock has 24k in the last week, mox has 3.5k
b) mock is a part of the standard library starting
On 07/24/2013 02:19 PM, Alex Gaynor wrote:
I think moving towards mock is a better long term strategy:
a) I don't you're correct that it's the most familiar for most python
developers. By PyPi installs (A TERRIBLE METRIC, but it's all we have).
Mock has 24k in the last week, mox has 3.5k
b)
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
: [openstack-dev] Usage of mox through out the Openstack project.
On 07/24/2013 02:19 PM, Alex Gaynor wrote:
I think moving towards mock is a better long term strategy:
a) I don't you're correct that it's the most familiar for most python
developers. By PyPi installs (A TERRIBLE METRIC, but it's
On Jul 24, 2013, at 1:12 PM, Chuck Short
chuck.sh...@canonical.commailto:chuck.sh...@canonical.com
wrote:
Hi,
The use of mox (https://pypi.python.org/pypi/mox/0.5.3) across the test suites
in the Openstack project is quite extensive. This is probably due to the fact
that it is the most
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
Message-
From: Russell Bryant rbry...@redhat.com
Sent: Wednesday, July 24, 2013 2:45pm
To: openstack-dev@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
13 matches
Mail list logo
