Hello team.
In my team we are testing different type checkers and Zuban qualifies quite well. I started working on the vscode-python extension to add support for Zuban, simply by replicating the Jedi support. Quite straightforward I must say.
However I have spotted in the Jedi code a few comments mentioning that Jedi might/will/should be pulled into its own extension. So I'm wondering if this is the general approach is to have the language servers out of the vscode-python extension, perhaps as pluggable modules? In which case, I should probably instead invest in ZubanLS' own extension.
The main advantage I saw in doing it inside vscode-python was to be able to reuse all the interpreter discovery machinery, to be able to detect Zuban inside virtual environments.
So this is not really a feature request but a request for guidance : what it the policy regarding adding language servers to this extension?
Thank you,
Sincerely
Hello team.
In my team we are testing different type checkers and Zuban qualifies quite well. I started working on the vscode-python extension to add support for Zuban, simply by replicating the Jedi support. Quite straightforward I must say.
However I have spotted in the Jedi code a few comments mentioning that Jedi might/will/should be pulled into its own extension. So I'm wondering if this is the general approach is to have the language servers out of the vscode-python extension, perhaps as pluggable modules? In which case, I should probably instead invest in ZubanLS' own extension.
The main advantage I saw in doing it inside vscode-python was to be able to reuse all the interpreter discovery machinery, to be able to detect Zuban inside virtual environments.
So this is not really a feature request but a request for guidance : what it the policy regarding adding language servers to this extension?
Thank you,
Sincerely