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. -- Kevin L. Mitchell <kevin.mitchell at rackspace.com>