[TIP] virtualenv 1.11 causes tox to fail while installing dependencies on Windows 7

[holger krekel]

On Tue, Jan 14, 2014 at 12:09 +0000, holger krekel wrote:
> On Tue, Jan 14, 2014 at 12:01 +0000, Paul Moore wrote:
> > On 14 January 2014 11:52, Marius Gedminas <marius at gedmin.as> wrote:
> > > I think Chris filed https://github.com/pypa/virtualenv/issues/539 about
> > > the same issue -- I still don't know if it's a tox bug, or a virtualenv
> > > bug.
> > 
> > Looks like a tox issue - see my comment on
> > https://github.com/pypa/virtualenv/issues/539
> 
> tox doesn't look for "pip-script.exe".  It looks for "pip.exe" in PATH,
> including the virtualenv's script dir on windows.  I can't spend much time
> to look into the issue this week but can hopefully try it next week.
> It's all quite confusing with the versions and upgrade issues ATM.

just checked and have to correct myself.  Indeed, pip-script.exe
is looked up on windows -- the code came in via a PR trying to
avoid locking the executable.  IIRC some folks wanted to be able
to install a different pip version via deps.

Anyone i just pused a tox-1.7.0.dev2 which you can install via:

    pip install --pre -i https://devpi.net/hpk/dev/ -U "tox>=1.7.0.dev2"

and it should now just lookup "pip" and no the -script one on windows.
I guess this means that one cannot upgrade pip from within tox anymore
on windows but it's a somewhat rare use case and might have only been
there for downgrading pip for python2.5 (which is not supported 
by tox anymore).

let me know if this fixes things.

best,
holger

> But Marius, Paul: to be sure i got it correctly: you are using tox-1.7.0.dev1
> and virtualenv-1.11 and pip-1.5 on your Jenkins/Windows server, right?
> And it works without jenkins and fails with it?
> 
> best,
> 
> holger
> 
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python
>