Hello, The contributing guide ( http://pytest.org/latest/contributing.html ) is still missing a couple of steps I'm afraid... I installed tox in my virtualenv and then ran "python runtox.py -e py27,py33,flakes" as advised. At the end of the run tox tells me: ERROR: py27: could not install deps [nose, mock] ERROR: py33: InterpreterNotFound: python3.3 ERROR: flakes: could not install deps [pytest-flakes>=0.2] I can manually pip install nose, mock and pytest-flakes, but I don't know how to make python3.3 (which I have installed from my OS repo) "visible" or available to this virtualenv. Any ideas? Thanks, Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/
Hi Brianna, On Wed, Apr 16, 2014 at 16:39 -0400, Brianna Laugher wrote:
Hello,
The contributing guide ( http://pytest.org/latest/contributing.html ) is still missing a couple of steps I'm afraid...
I installed tox in my virtualenv and then ran "python runtox.py -e py27,py33,flakes" as advised. At the end of the run tox tells me:
ERROR: py27: could not install deps [nose, mock] ERROR: py33: InterpreterNotFound: python3.3 ERROR: flakes: could not install deps [pytest-flakes>=0.2]
I can manually pip install nose, mock and pytest-flakes, but I don't know how to make python3.3 (which I have installed from my OS repo) "visible" or available to this virtualenv. Any ideas?
It should be on the PATH, so invoking "python3.3" should basically work. As to the "could not install deps" error, could you use the "-v" option and/or attach the full tox output log? best, holger
Thanks, Brianna
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
OK, I will do that. Another question, how can I build the docs? Brianna On 16 April 2014 16:44, holger krekel <holger@merlinux.eu> wrote:
Hi Brianna,
On Wed, Apr 16, 2014 at 16:39 -0400, Brianna Laugher wrote:
Hello,
The contributing guide ( http://pytest.org/latest/contributing.html ) is still missing a couple of steps I'm afraid...
I installed tox in my virtualenv and then ran "python runtox.py -e py27,py33,flakes" as advised. At the end of the run tox tells me:
ERROR: py27: could not install deps [nose, mock] ERROR: py33: InterpreterNotFound: python3.3 ERROR: flakes: could not install deps [pytest-flakes>=0.2]
I can manually pip install nose, mock and pytest-flakes, but I don't know how to make python3.3 (which I have installed from my OS repo) "visible" or available to this virtualenv. Any ideas?
It should be on the PATH, so invoking "python3.3" should basically work. As to the "could not install deps" error, could you use the "-v" option and/or attach the full tox output log?
best, holger
Thanks, Brianna
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
On Wed, Apr 16, 2014 at 16:56 -0400, Brianna Laugher wrote:
OK, I will do that. Another question, how can I build the docs?
"tox -e doc" should work. Otherwise installing sphinx and going to "doc/en" and typing "make html" should work. Or on windows some sphinx-build command that you find in the tox.ini file. best, holger
Brianna
On 16 April 2014 16:44, holger krekel <holger@merlinux.eu> wrote:
Hi Brianna,
On Wed, Apr 16, 2014 at 16:39 -0400, Brianna Laugher wrote:
Hello,
The contributing guide ( http://pytest.org/latest/contributing.html ) is still missing a couple of steps I'm afraid...
I installed tox in my virtualenv and then ran "python runtox.py -e py27,py33,flakes" as advised. At the end of the run tox tells me:
ERROR: py27: could not install deps [nose, mock] ERROR: py33: InterpreterNotFound: python3.3 ERROR: flakes: could not install deps [pytest-flakes>=0.2]
I can manually pip install nose, mock and pytest-flakes, but I don't know how to make python3.3 (which I have installed from my OS repo) "visible" or available to this virtualenv. Any ideas?
It should be on the PATH, so invoking "python3.3" should basically work. As to the "could not install deps" error, could you use the "-v" option and/or attach the full tox output log?
best, holger
Thanks, Brianna
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
Error logs from tox: https://gist.github.com/pfctdayelise/b8e4b249f3ae2b0103ab It seems like tox was happy to install sphinx when I built the docs. cheers Brianna On 16 April 2014 16:58, holger krekel <holger@merlinux.eu> wrote:
On Wed, Apr 16, 2014 at 16:56 -0400, Brianna Laugher wrote:
OK, I will do that. Another question, how can I build the docs?
"tox -e doc" should work. Otherwise installing sphinx and going to "doc/en" and typing "make html" should work. Or on windows some sphinx-build command that you find in the tox.ini file.
best, holger
Brianna
On 16 April 2014 16:44, holger krekel <holger@merlinux.eu> wrote:
Hi Brianna,
On Wed, Apr 16, 2014 at 16:39 -0400, Brianna Laugher wrote:
Hello,
The contributing guide ( http://pytest.org/latest/contributing.html) is still missing a couple of steps I'm afraid...
I installed tox in my virtualenv and then ran "python runtox.py -e py27,py33,flakes" as advised. At the end of the run tox tells me:
ERROR: py27: could not install deps [nose, mock] ERROR: py33: InterpreterNotFound: python3.3 ERROR: flakes: could not install deps [pytest-flakes>=0.2]
I can manually pip install nose, mock and pytest-flakes, but I don't know how to make python3.3 (which I have installed from my OS repo) "visible" or available to this virtualenv. Any ideas?
It should be on the PATH, so invoking "python3.3" should basically work. As to the "could not install deps" error, could you use the "-v" option and/or attach the full tox output log?
best, holger
Thanks, Brianna
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
On Wed, Apr 16, 2014 at 17:11 -0400, Brianna Laugher wrote:
Error logs from tox: https://gist.github.com/pfctdayelise/b8e4b249f3ae2b0103ab
It seems like tox was happy to install sphinx when I built the docs.
Seems like "devpi.net" is having troubles providing the correct package or so currently (not sure why). It is used by "runtox.py". What happens if you delete the line in "runtox.py" containing "-i", "http:/..."? holger
cheers Brianna
On 16 April 2014 16:58, holger krekel <holger@merlinux.eu> wrote:
On Wed, Apr 16, 2014 at 16:56 -0400, Brianna Laugher wrote:
OK, I will do that. Another question, how can I build the docs?
"tox -e doc" should work. Otherwise installing sphinx and going to "doc/en" and typing "make html" should work. Or on windows some sphinx-build command that you find in the tox.ini file.
best, holger
Brianna
On 16 April 2014 16:44, holger krekel <holger@merlinux.eu> wrote:
Hi Brianna,
On Wed, Apr 16, 2014 at 16:39 -0400, Brianna Laugher wrote:
Hello,
The contributing guide ( http://pytest.org/latest/contributing.html) is still missing a couple of steps I'm afraid...
I installed tox in my virtualenv and then ran "python runtox.py -e py27,py33,flakes" as advised. At the end of the run tox tells me:
ERROR: py27: could not install deps [nose, mock] ERROR: py33: InterpreterNotFound: python3.3 ERROR: flakes: could not install deps [pytest-flakes>=0.2]
I can manually pip install nose, mock and pytest-flakes, but I don't know how to make python3.3 (which I have installed from my OS repo) "visible" or available to this virtualenv. Any ideas?
It should be on the PATH, so invoking "python3.3" should basically work. As to the "could not install deps" error, could you use the "-v" option and/or attach the full tox output log?
best, holger
Thanks, Brianna
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
That worked...mostly. https://gist.github.com/pfctdayelise/b8e4b249f3ae2b0103ab#file-tox-output-wi... Is the "flakes: commands failed" something to worry about? ERROR: InvocationError: '/home/brianna/workspace/pytest/.tox/flakes/bin/py.test --flakes -m flakes _pytest testing' __________________________________________________________________________________________________ summary __________________________________________________________________________________________________ py27: commands succeeded ERROR: py33: InterpreterNotFound: python3.3 ERROR: flakes: commands failed Brianna On 16 April 2014 17:16, holger krekel <holger@merlinux.eu> wrote:
On Wed, Apr 16, 2014 at 17:11 -0400, Brianna Laugher wrote:
Error logs from tox: https://gist.github.com/pfctdayelise/b8e4b249f3ae2b0103ab
It seems like tox was happy to install sphinx when I built the docs.
Seems like "devpi.net" is having troubles providing the correct package or so currently (not sure why). It is used by "runtox.py". What happens if you delete the line in "runtox.py" containing "-i", "http:/..."?
holger
cheers Brianna
On 16 April 2014 16:58, holger krekel <holger@merlinux.eu> wrote:
On Wed, Apr 16, 2014 at 16:56 -0400, Brianna Laugher wrote:
OK, I will do that. Another question, how can I build the docs?
"tox -e doc" should work. Otherwise installing sphinx and going to "doc/en" and typing "make html" should work. Or on windows some sphinx-build command that you find in the tox.ini file.
best, holger
Brianna
On 16 April 2014 16:44, holger krekel <holger@merlinux.eu> wrote:
Hi Brianna,
On Wed, Apr 16, 2014 at 16:39 -0400, Brianna Laugher wrote:
Hello,
The contributing guide ( http://pytest.org/latest/contributing.html) is still missing a couple of steps I'm afraid...
I installed tox in my virtualenv and then ran "python runtox.py -e py27,py33,flakes" as advised. At the end of the run tox tells me:
ERROR: py27: could not install deps [nose, mock] ERROR: py33: InterpreterNotFound: python3.3 ERROR: flakes: could not install deps [pytest-flakes>=0.2]
I can manually pip install nose, mock and pytest-flakes, but I don't know how to make python3.3 (which I have installed from my OS repo) "visible" or available to this virtualenv. Any ideas?
It should be on the PATH, so invoking "python3.3" should basically work. As to the "could not install deps" error, could you use the "-v" option and/or attach the full tox output log?
best, holger
Thanks, Brianna
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
On 16 April 2014 16:44, holger krekel <holger@merlinux.eu> wrote:
I can manually pip install nose, mock and pytest-flakes, but I don't know how to make python3.3 (which I have installed from my OS repo) "visible" or available to this virtualenv. Any ideas?
It should be on the PATH, so invoking "python3.3" should basically work.
Do you mean calling runtox.py with the right python version? No luck there either: (pytest)brianna@montreal:~/workspace/pytest$ which python3.4 /usr/bin/python3.4 (pytest)brianna@montreal:~/workspace/pytest$ python3.4 runtox.py -v -e py27,py34,flakes /usr/bin/python3.4: No module named tox (pytest)brianna@montreal:~/workspace/pytest$ which python3 /usr/bin/python3 (pytest)brianna@montreal:~/workspace/pytest$ python3 runtox.py -v -e py27,py34,flakes /usr/bin/python3: No module named tox Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/
On Wed, Apr 16, 2014 at 17:39 -0400, Brianna Laugher wrote:
On 16 April 2014 16:44, holger krekel <holger@merlinux.eu> wrote:
I can manually pip install nose, mock and pytest-flakes, but I don't know how to make python3.3 (which I have installed from my OS repo) "visible" or available to this virtualenv. Any ideas?
It should be on the PATH, so invoking "python3.3" should basically work.
Do you mean calling runtox.py with the right python version? No luck there either:
(pytest)brianna@montreal:~/workspace/pytest$ which python3.4 /usr/bin/python3.4 (pytest)brianna@montreal:~/workspace/pytest$ python3.4 runtox.py -v -e py27,py34,flakes /usr/bin/python3.4: No module named tox (pytest)brianna@montreal:~/workspace/pytest$ which python3 /usr/bin/python3 (pytest)brianna@montreal:~/workspace/pytest$ python3 runtox.py -v -e py27,py34,flakes /usr/bin/python3: No module named tox
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. holger
Brianna
-- They've just been waiting in a mountain for the right moment: http://modernthings.org/
On 16 April 2014 17:43, holger krekel <holger@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 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. Brianna -- They've just been waiting in a mountain for the right moment: http://modernthings.org/
On Wed, Apr 16, 2014 at 17:58 -0400, Brianna Laugher wrote:
On 16 April 2014 17:43, holger krekel <holger@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@python.org https://mail.python.org/mailman/listinfo/pytest-dev
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@merlinux.eu> wrote:
On Wed, Apr 16, 2014 at 17:58 -0400, Brianna Laugher wrote:
On 16 April 2014 17:43, holger krekel <holger@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@python.org https://mail.python.org/mailman/listinfo/pytest-dev
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
On 16 April 2014 22:58, Brianna Laugher <brianna.laugher@gmail.com> 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
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 <flub@devork.be> wrote:
On 16 April 2014 22:58, Brianna Laugher <brianna.laugher@gmail.com> 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/
participants (4)
-
Brianna Laugher -
Floris Bruynooghe -
holger krekel -
Marc Abramowitz