| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@microsoft-github-policy-service agree |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for the PR! Would be great to get a test for this item and then otherwise a few comments if you could address. Additionally linting is failing if you could get that fixed too- thanks!
Sorry, something went wrong.
|
One other question, did you have an issue regarding this feature? We link an issue to track status and the issue usually outlines the problem and steps to reproduce for tracking. I can make one if not |
Sorry, something went wrong.
I would like to, for the test, I should take a look to see if there is a good way for it.
That's my fault, I forgot to run prettier. |
Sorry, something went wrong.
In fact, there is no direct issue for this, but I got a reminder when I raise the issue davidhalter/jedi#2084, as there is no way for me to test the change. |
Sorry, something went wrong.
…vironments As this extension uses an internal Jedi LSP, it is hard for the users to change the jedi setting to adapt various requirements. And in some cases, the user require a specific version of the Jedi, which is hard to change as it is embedded. Add a new configuration property to allow the users to use Jedi LSP in their system environment or virtual environments, and auto fallback to the internal version if the external version is not found. Signed-off-by: Inochi Amaoto <inochiama@gmail.com>
Any suggestion for the test? I have no idea for this PR as it is very simple. It is just add a new variable and chained to the script. |
Sorry, something went wrong.
|
Eleanor Boyd (@eleanorjboyd) I also change the key to the python.jedi.useJediInEnvPath, as previous key python.languageServer.useJediInEnvPath is broken after rebasing to main branch. Any idea for this? |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
As this extension uses an internal Jedi LSP, it is hard for the users to change the jedi setting to adapt various requirements. And in some cases, the user require a specific version of the Jedi, which is hard to change as it is embedded.
Add a new configuration property to allow the users to use Jedi LSP in their system environment or virtual environments, and auto fallback to the internal version if the external version is not found.
fixes: #25722