[pytest-dev] Setting up tox

[Marc Abramowitz]

In order to fix the python3.3 error, you just need to get it so that
"python3.3" works normally from the shell.

First, Python 3.3 needs to be installed. Tox doesn't install the Pythons
for you, like say, pythonbrew. I don't know what distro you're on, but for
Ubuntu, I typically set up the "deadsnakes" PPA (
https://launchpad.net/~fkrull/+archive/deadsnakes) and then I can `sudo
apt-get install python3.3-dev`. The steps look something like this on
Ubuntu:

sudo apt-get install python-software-properties  # This is to get
add-apt-repository, which you may or may not already have
sudo add-apt-repository ppa:fkrull/deadsnakes
sudo apt-get update
sudo apt-get install python3.3-dev

Of course, I'm just guessing that you might have Ubuntu because it's
popular. If I'm wrong, the steps will be completely different. If you have
a different distro, you can Google around or maybe post again and maybe
someone else can tell you how they do it.

Also, "python3.3" needs to be in $PATH. Most likely if you install with a
package manager like apt-get or yum, it will be automatically in the $PATH.
It might not be if you build from source.


On Wed, Apr 16, 2014 at 3:56 PM, holger krekel <holger at merlinux.eu> wrote:

> On Wed, Apr 16, 2014 at 17:58 -0400, Brianna Laugher wrote:
> > On 16 April 2014 17:43, holger krekel <holger at merlinux.eu> wrote:
> >
> > > No, i mean that "python3.3" should be on the path because tox.ini
> > > defines that tests should work against the "py33" environment which
> > > implies a working "python3.3" interpreter.  How you invoke "runtox.py"
> > > is a different thing and it does need tox installed in the interpreter
> > > you are invoking the script with.
> > >
> >
> > So, what is the answer?
> > 1) Install multiple pythons in a single virtualenv, somehow
>
> no.  You cannot really install multiple python version..
>
> > 2) Install tox system-wide, in which case how does it know about my
> > development version of py.test? (from current working dir?)
>
> > The contributing guide does say to install tox in the virtualenv. I am
> > happy to update it...once I know what I am actually supposed to do.
>
> I usually install tox in a virtualenv itself.  If i then run tox, it
> will create its own separate virtualenv environments and it uses the
> tox.ini-specified python interpreters for creating them.  tox will
> then install pytest in those separate virtualenvs and then execute
> the commands specified in tox.ini.  From your output it seems that
> this successfully worked for python2.7 but not for python3.3 and i
> suspected this is because "python3.3" is not in your PATH environment
> varaible and therefore tox cannot find it.
>
> hope this clarifies and sorry for failing to explain this more properly,
> holger
>
>
> >
> > Brianna
> >
> > --
> > They've just been waiting in a mountain for the right moment:
> > http://modernthings.org/
>
> > _______________________________________________
> > Pytest-dev mailing list
> > Pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
>
> _______________________________________________
> Pytest-dev mailing list
> Pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20140416/d532f0f1/attachment.html>