search

alfredodeza / pytest.vim

Runs your UnitTests with py.test displaying red/green bars and errors
274 stars 39 forks source link

can't provide alternative py.test #4

Closed mrsipan closed 13 years ago

mrsipan commented 13 years ago

Is it posible to provide an alternative py.test

alfredodeza commented 13 years ago

I am not sure what you mean by an alternative py.test. Could you please elaborate on that?

mrsipan commented 13 years ago

Thanks for answering. Basically, I would like to use the py.test of my buildout project which has a path that pytest.vim can't find. So I wonder if I can specify where the py.test command is located.

alfredodeza commented 13 years ago

Ah, ok... well basically, what is happening is not that pytest.vim doesn't know which py.test executable to use, it is that Vim is unaware of this.

This usually happens when you are in a virtualenv and Vim was not called when that environment was activated.

You can replicate this behavior by creating a virtualenv, activate it, install py.test, call vim and run py.test (it works)

Then quit out of Vim, deactivate the virtualenv, call Vim again and try calling py.test (it doesn't work, py.test is not found).

The problem with providing something that would fix what you are experiencing is that it is hard-coding a path to an executable that may change (imagine someone with multiple projects).

I am closing this ticket as I am pretty sure this is what is happening. If you feel this is not the case please re-open it with more details as to what you think is happening and how can I replicate it.

mrsipan commented 13 years ago

It is. Thanks.