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, opportunistically, as tests are > being updated anyway. (Or if someone *really* wants to take this on as > a project ...)
Agreed. I will -1 every new patch coming with mox inside. :-) And I'll probably do some conversion for Oslo anyway. -- Julien Danjou ;; Free Software hacker ; freelance consultant ;; http://julien.danjou.info
signature.asc
Description: PGP signature
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
