[TIP] problems with tox/python 3.3/ windows 7

Chris Withers chris at simplistix.co.uk
Thu Mar 6 14:57:55 PST 2014

Hi All,

I've been having problems on Windows 7 for quite a while now, the issues 
I was having appear to have changed, and the one that's left is now as 
described here:


This is just running in a dos box, no Jenkins involved, using Python 
3.3.0 on Windows 7. <tools path> and <workspace> are just to get the 
text shorter.

I see this:

<tools path>\Scripts\python.exe -c "import pip; pip.main();" install 
--upgrade tox


Requirement already up-to-date: tox in <tools path>\lib\site-packages
Requirement already up-to-date: virtualenv>=1.11.2 in <tools 
path>\lib\site-packages (from tox)
Requirement already up-to-date: py>=1.4.17 in <tools 
path>\lib\site-packages (from tox)

Looking at versions:

Python 3.3.0 (v3.3.0:bd8afb90ebf2, Sep 29 2012, 10:55:48) [MSC v.1600 32 
bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
 >>> import tox
 >>> tox.__version__
 >>> import py
 >>> py.__version__
 >>> import virtualenv
 >>> virtualenv.__version__

When I attempt to do:

<tool path>\Scripts\python.exe -c "import tox; tox.cmdline();" -
c tox.ini -v
using tox.ini: <workspace>\tox.ini
using tox-1.7.0 from <tools path>\lib\site-packages\tox\__init__.py
py26 create: <workspace>\.tox\py26
ERROR: InvocationError: could not find executable 'virtualenv'

Stepping through _venv.VirtualEnv.getcommandpath suggests that 
py.path.local.sysfind is being called with:

(Pdb) self.envconfig.envbindir

...rather than the local('<tools>\\Scripts') I would expect.

This is the call to create .tox\py26, so its scripts will not exist yet.

The tox.ini in question is here:


Has anyone seen anything similar? I'm finding this really quite 
impenetrable :-(


Simplistix - Content Management, Batch Processing & Python Consulting
            - http://www.simplistix.co.uk

More information about the testing-in-python mailing list