Daniel Hahler
Daniel Hahler
> system('pipenv --venv') pipenv is slow in general, and `system()` should be avoided in general. I suggest having your `$PATH` setup properly (as with `pipenv --shell` (IIRC) or through some...
> I would like jedi to (automatically) detect venvs in the working directory from within neovim/vim. Setting `$VIRTUAL_ENV` is the usual/canonical way to do so.. :) I am using the...
@petobens Setting `$VAR` in Vim does not set it for the Python process, but the following could be used: `:py3 import os; os.environ['VIRTUAL_ENV'] = '/path/to/venv'`.
@petobens Anyway, have you tried this PR after all, which is supposed to make this simpler? (but also needs updating / more work)
Rebased, without the updates to jedi/parso which I assume have landed already.
@aliceh75 Thanks for review. I've rebased it now. As for completing from certain paths there is `g:jedi#environment_paths` already, which (IIRC) should do what you want. E.g. `:let g:jedi#environment_paths = [expand('~/.pyenv/versions')]`...
@petobens > My main problem (with your changes and with vim and venvs in general) is how to disable a virtual env: > i) Start vim/nvim > ii) Use `JediUseEnvironment`...
@syphar sure, give it a try. (I've just rebased it on master)
@petobens Thanks for the feedback. I also think this should be ready, but IIRC needs a last round of polishing I guess.
#652 is only for call signatures, not docs. @blayz3r something like this could be done. We should keep that in mind with #652 (so that functions can be shared etc).