-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Python Module Detected #36
Comments
Also occurs with NVIM v0.4.3 |
Yup I'm getting this. I had installed isort with In the end I uninstalled the plugin and just added the following to my vim file: autocmd BufWritePost *.py :!isort % |
For a homebrew install, remove The issue appears to be the
More sophisticated plugins, like black get around this by the plugin itself installing their dependancies in venvs and appending their special install path to sys.path on plugin load. |
I think this is related to using pyenv. Isort plugin seems to use system python on startup. |
I had a similar issue which I had to find the actual python binary vim was using and install it in there.
I am using pyenv and virtualenv which may have messed up my paths and for some reason vim-isort could not find the "correct" python version when using vim-isort/ftplugin/python_vimisort.vim Line 12 in 05d709d
|
I had the same issue that @zsoobhan described above but that solution didn't work for me because even the command I manage it installing the neovim package into the
|
On Mac M1, I was also getting this issue. This was my solution. Check to see if under:
python & python3 have + instead of -.
|
I am running into this - I have |
Hi there,
I am getting the error
No isort python module detected, you should install it. More info at https://github.com/fisadev/vim-isort
when trying to execute isort within Vim. Isort has correctly been pip installed:and
isort example.py
indeed does sort the imports.Vim version is 8.1.
(Searched previous issues and none of the solutions worked. I have pip installed
isort
through both python3.8 and 2.7).The text was updated successfully, but these errors were encountered: