[TIP] Using tox with wine

[Marius Gedminas]

Sometimes I find myself debugging cross-platform issues by running my
tests under Wine on a Linux box.  This works:

  wget http://www.python.org/ftp/python/2.7.3/python-2.7.3.msi
  wine start python-2.7.3.msi
    # the usual next next next finish make-work
  ~/.wine/drive_c/Python27/python.exe /usr/share/pyshared/virtualenv.py wenv
  wenv/Scripts/pip.exe install nose # etc.
  wenv/Scripts/python.exe setup.py develop
  wenv/Scripts/nosetests.exe

I would like to teach tox to do all this for me.  Any hints/ideas?

  [testenv:wine]
  basepython = {env:HOME}/.wine/drive_c/Python27/python.exe

_almost_ works: the virtualenv is created, and it contains working
Scripts/pip.exe and Scripts/python.exe.  But then tox tries to install
stuff using /usr/bin/pip instead of .tox/wine/Scripts/pip.exe and, of
course, fails.

Can I somehow tell tox to use a different pip command to install stuff?

Marius Gedminas
-- 
Sometimes all the news comment allowing has done is revealed that yes, even the
most backwards, backwater, babblethumping loons can afford internet access.
        -- nicosian on livejournal
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20120906/2eb21dca/attachment.pgp>