[TIP] tox-1.2: some bug fixes for the virtualenv-based generic test runner

holger krekel holger at merlinux.eu
Fri Nov 11 11:21:06 PST 2011

On Fri, Nov 11, 2011 at 18:28 +0000, Michael Foord wrote:
> On 11 Nov 2011, at 15:26, holger krekel wrote:
> >>> I am happy to announce tox 1.2, now using and depending on the latest
> >>> virtualenv code and containing some bug fixes.  TOX automates tedious
> >>> test activities driven from a simple ``tox.ini`` file, including:
> >>> 
> >> 
> >> When I run tox 1.2 with Python 2.7 my Python 3 (3.1 / 3.2) tests no longer run - they are picking up the wrong virtualenv.py. 
> > 
> > Just to be sure, which virtualenv version is this?
> > 
> > On my OSX 10.6, creating the py31 env work nicely like this:

> Well it looks like your virtualenv is installed with easy_install (inside an egg) whereas mine was done with pip. My suspicion is that this is the cause of the problem - somehow that location is on the path for the Python 3 environments.

I created a new virtualenv and pip-installed virtualenv and again it
works for me:

hpk at noco:~/p/tox$ tox --recreate -e py31 --notest
_____________________________ [tox sdist] _____________________________
[TOX] ***creating sdist package
[TOX] /Users/hpk/p/tox$ /Users/hpk/venv/1/bin/python setup.py sdist --formats=zip --dist-dir .tox/dist >.tox/log/0.log
[TOX] ***copying new sdistfile to '/Users/hpk/.tox/distshare/tox-1.2.zip'
_________________________ [tox testenv:py31] __________________________
[TOX] ***recreating virtualenv py31 (configchange/incomplete install detected)
[TOX] /Users/hpk/p/tox/.tox$ /Library/Frameworks/Python.framework/Versions/3.1/bin/python3.1 /Users/hpk/venv/1/lib/python2.7/site-packages/virtualenv.py --no-site-packages py31 >py31/log/0.log

It also uses the virtualenv.py like it did in your version.
This is virtualenv-1.6.4.  Can you create a new virtualenv and try
to reproduce the problem on your side?


More information about the testing-in-python mailing list