On Tue, 2013-11-12 at 09:33 -0500, Cole Robinson wrote:
Ah, good call. I had some really old cache there, you can tell I don't use pip/virtualenv much :)
:)
Without that, when the python3 init failed, the script continued on and ran the tests as usual, which all pass since we were still running in the python2 env, which was quite misleading. There may be a better place to stick the 'exit 1' or similar.
Hmm, might need to move the check elsewhere, since the run-tests script is running in a sub-shell it should be file, but this will cause issues if a we are activating the environment manually.
Will submit a patch soon. :)