[TIP] Bug when testing nested virtual environments under Tox
andre.l.caron at gmail.com
Mon Jan 18 05:19:57 PST 2016
Also seems like a bug to me, but I don't know if the compatibility between
the two implementations is even somebody's goal at the moment.
I'm getting these results on OSX, I haven't tried Debian nor Windows yet.
I guess I'll move this info to Python's bug tracker because it's clearly
not an issue with Tox per se :-)
Thanks for the help!
On Mon, Jan 18, 2016 at 12:23 AM, Florian Bruhin <me at the-compiler.org>
> * André Caron <andre.l.caron at gmail.com> [2016-01-17 23:34:49 -0500]:
> > Yup, adding "virtualenv==13.1.2" in my "deps" section and using "python
> > virtualenv" instead of "python -m venv" fixes it...
> > While totally understandable, this is rather surprising: I would have
> > expected the official venv implementation to be based on the popular
> > virtualenv package.
> This still sounds a bug in either virtualenv or venv to me. I'm not
> sure which one ;)
> > I'm trying to stick to the now standard package since I'm only targetting
> > Python 3.5+ anyways, but I can't use it when I use Tox to test my
> FWIW, I had various other trouble with the stdlib venv, mainly because
> Debian/Ubuntu patch it and break things in the process.
> Not sure if it's better nowadays, but I ended up using virtualenv
> instead which worked better for me.
> 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/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the testing-in-python