[TIP] Using tox with wine

[Ronny Pfannschmidt]

Hi Marius,

currently there is no support for different installers.

There is a vague plan for a upcoming re-factoring
that also allows more kinds of installers.

But its not clear when implementation of that will start.

Making tox wine-aware could be a neat addition
to its general capabilities - could you report
a feature request on the bts?

best regards,
Ronny Pfannschmidt

On 09/06/2012 12:35 PM, Marius Gedminas wrote:
> 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
>
>
>
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python