On 17 February 2014 13:50, Mike Spreitzer <mspre...@us.ibm.com> wrote: > Robert Collins <robe...@robertcollins.net> wrote on 02/16/2014 05:26:50 PM: > >> I would have expected run_tests.sh to tox which creates a venv, but >> heat seems different. So you'll need to install testrepository via >> your system tox, not one from a venv. > > > I don't think I have a system tox. `pip list | grep -i tox` comes up empty. > Should I be looking for a system tox in some other way? I'm a little > unclear on what you are saying here.
s/system tox/system pip/. >> The 'd' is because you're human-reading a binary protocol (which the >> testrepository trunk fixes). Try the import without the 'd'. Also be >> sure to be trying the import within the tox venv, which run_tests will >> have triggered. > > > If I take the 'd' off then that import succeeds like all the others, > when tried manually in the venv created by run_tests.sh -V. I'm unclear - are you running 'run_tests.sh' or 'run_tests.sh -V'. *either way*, you need to be using the matching pip to install testrepository, and you need to be using the matching Python to test imports. -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev