Support py2 and py3 (or auto pick python version from virtual env) about pytest-vim-compiler HOT 5 CLOSED

This did the trick for me:

CompilerSet makeprg=.venv/bin/python\ -m\ pytest\ --tb=short\ -q

Note that .venv/ is my virtual env.

from pytest-vim-compiler.

Currently it uses just py.test, which should also get picked up from the $PATH, no?
Don't you have the bin dir of your $VIRTUAL_ENV there?

from pytest-vim-compiler.

My virtualenv is in .venv/ of each project. But there was a py.test in the site-packages (which I thought should not be used) and that was a 2.7 version. After uninstalling that version the correct py.test from the venv was used.

(I also had to deactivate some plugins but that is unrelated.)

Thanks!

from pytest-vim-compiler.

@sotte

In case you might have missed this: the recommended way to use virtualenv is to activate it before working on the project. Activating a virtualenv will add ENV/bin to your $PATH, which will allow you to launch ENV/bin/py.test by executing py.test.

Automagically detecting local virtualenv might be good. But there's no single most popular way to organize virtualenv as far as I know:

• .venv/ is a reasonable choice I guess.
• I'm using virtualenvwrapper, which works well for me.
• At where I work, we're installing virtualenv in venv/ and NOT gonna activate it. Instead, we have an in-house PAAS which requires me to use a custom script to launch any executables in the virtualenv. Totally non-standard, but gotta live with it.

So um, I believe activating virtualenv before launching vim should be good enough for this vim compiler works for most people.

from pytest-vim-compiler.

@5long ya, the venv is activated of course, all the dependencies are picked up and whatnot. Thanks though!

from pytest-vim-compiler.