0

When I start VIM after activating an Python virtulenv, Python plugins can't find their modules, because they are installed in the system, not in the project's virtualenv.

I am using the aw-watcher-vim plugin, which uses a Python library.

When I create a virtualenv and activate it:

virtualenv -p python3 my_env
. my_env/bin/activate

VIM can't find the module at /usr/local/lib/python3.6/dist-packages/aw_core/ anylonger and prints the following errors:

['Traceback (most recent call last):',
'  File "~/.dot-file-repo/neovim/plugged/aw-watcher-vim/plugin/vimwatcher.py", line 6 , in <module>',
'    from aw_core.log import setup_logging',
'ModuleNotFoundError: No module named ''aw_core''',
'']

(Slightly reformated for readablity.)

It would be nice to use autocompletion using the code from the virtualenv (via Jedi or so), but let the other plugins find their Python modules. Is there a good solution to this use case?

lumbric
  • 7,644
  • 7
  • 42
  • 53
  • Possible duplicate of [How to import a globally installed package to virtualenv folder](https://stackoverflow.com/questions/13992214/how-to-import-a-globally-installed-package-to-virtualenv-folder) – phd Jan 27 '19 at 20:16
  • https://stackoverflow.com/search?q=%5Bvirtualenv%5D+access+global+site-packages – phd Jan 27 '19 at 20:16

1 Answers1

1

While some comments suggest to import globally instaled pacckages to virtualenv, I'd suggest to set options in /vimrc to use the system python:

set pythondll=/usr/bin/python
set pythonthreedll=/usr/bin/python3

or whatever your system python is.

The advantage is that you virtual envs are untouched and are used according to your needs.

Artem Trunov
  • 1,340
  • 9
  • 16