OK with a fresh head this morning... it was PEBCAK as usual. I had installed python3 (which was3.2) and python3.4, but not python3.3. Now I have installed python3.3 all is working as advertised. Sorry for the confusion and thanks everyone for your help.
Brianna On 17 April 2014 04:38, Floris Bruynooghe <[email protected]> wrote: > On 16 April 2014 22:58, Brianna Laugher <[email protected]> wrote: > > So, what is the answer? > > 1) Install multiple pythons in a single virtualenv, somehow > > The multiple python's need to be on the system, system wide installs > are fine. Personally I use the system provided ones plus, on ubuntu, > the deadsnakes ppa for all other python versions. On my Debian boxes > I build the other versions from scratch. But most systems ship with a > 2.x and a 3.x version by now which is a good enough start. > > > 2) Install tox system-wide, in which case how does it know about my > > development version of py.test? (from current working dir?) > > Contrary to Holger I tend to install tox in my system's python using > "pip install -U --user tox" and use that to run the py.test tests. It > works with the current working dir to find the package under test > indeed, then it packs it up and deploys it in a few virtualenvs it > manages itself. > > > Hope that helps, > Floris > > -- > Debian GNU/Linux -- The Power of Freedom > www.debian.org | www.gnu.org | www.kernel.org > -- They've just been waiting in a mountain for the right moment: http://modernthings.org/
_______________________________________________ Pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
