[TIP] Bug when testing nested virtual environments under Tox

[André Caron]

Thanks for the quick reply :-)

Just ran another experiment.  I tried to create the first environment using
the same command as Tox, but leave the 2nd unchanged.  It seems like Tox
uses the 3rd-party virtualenv package while I was trying to use the
built-in venv package provided since Python 3.3+.   Apparently, they don't
like to mix.

If I change both to use the 3rd-party virtualenv package, it seems to work
(at least in a shell script).  I'll try to get that in my full
implementation to confirm.

Cheers,

André

On Sun, Jan 17, 2016 at 11:23 PM, Florian Bruhin <me at the-compiler.org>
wrote:

> * André Caron <andre.l.caron at gmail.com> [2016-01-17 23:09:04 -0500]:
> > Since it only fails under Tox, I'm assuming Tox is doing something that
> > affects the behavior of virtual environment creation, but I can't figure
> > out what.
>
> Odd... I can reproduce it and first thought it might be because of
> environment filtering, but adding "passenv = *" doesn't change
> anything.
>
> Florian
>
> --
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>          I love long mails! | http://email.is-not-s.ms/
>
> _______________________________________________
> testing-in-python mailing list
> testing-in-python at lists.idyll.org
> http://lists.idyll.org/listinfo/testing-in-python
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/testing-in-python/attachments/20160117/42fef9be/attachment.htm>