You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
I use mspyls with Neovim Language Client. The settings are statically defined in a settings.json and so is the InterpreterPath. I work with a lot of virtual environments so I want to define my Python binary location based on the project I'm working in.
There is no such support at the moment, though I've personally considered a change (not sure in which issue) where providing no path/version will call out to python in PATH and fill in the required info, so if you run nvim with an environment activated this would be handled for you.
That would be a solution, I always open my vim buffers inside a virtualenv so the Python Path would be correct. I search in the issues to find the appropriate one.
Note that the method there isn't cross-platform; the correct method would be to look up PATH and then split on Path.PathSeparator to search for python.
I use mspyls with Neovim Language Client. The settings are statically defined in a settings.json and so is the InterpreterPath. I work with a lot of virtual environments so I want to define my Python binary location based on the project I'm working in.
settings.json
Now my question arises, is it possible to define the InterpreterPath using terminal arguments?
For example:
Or is there a more simpler solution to my problem?
The text was updated successfully, but these errors were encountered: