neovim python-client when using in a virtualenv
See original GitHub issueThis is not a bug, but a documentation suggestion.
I tried out neovim with YouCompleteMe and all my python plugins (python-mode, virtualenv) enabled. Everything works fine and all vim plugins are loaded.
But when someone works within a virtualenv the thing is breaking. My solution to this is to install the python client into a virtualenv itself and setting PYTHONPATH=~/.virtualenvs/neovim/lib/python2.7/site-packages
Issue Analytics
- State:
- Created 9 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
neovim uses virtualenv python version - Reddit
Hi, I want nvim to autodetect and use the correct version of python. I think something that can work when I work with...
Read more >Provider - Neovim docs
To use Python plugins, you need the "pynvim" module. Run :checkhealth to see if you already have it (some package managers install the...
Read more >neovim can not find python correctly because of virtualenv or ...
I got the UltiSnips error message to go away by (re)installing the neovim package, inside the current environment, with pip install neovim ....
Read more >Is there a way to have some kind of virtual environment for ...
For example, you can try AstroNVim without touching any configuration by running their official Docker instance with the following command:
Read more >Installation — Neovim Python Client documentation
If you only use one of python2 or python3, it is enough to install that version. If you follow Neovim HEAD, make sure...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It looks like pointing neovim to my Homebrew Python installation did it:
let g:python_host_prog = '/usr/local/bin/python'
I think this was resolved by
:CheckHealth
, @tweekmonster LMK if not.