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
The VSCode extension will no longer automatically inject the currently active Python interpreter into the configuration sent to the server.
4
+
It is now required for all users to set the `esbonio.sphinx.pythonCommand` option, either in your VSCode settings, or in your project's `pyproject.toml` file.
5
+
6
+
This makes VSCode's behavior more predicable and brings it in line with how other editors behave.
7
+
It also encourages the sharing of project configuration settings, which is particuarly useful if you use an [environment manager](https://docs.esbon.io/en/latest/lsp/howto/use-esbonio-with.html)
Copy file name to clipboardExpand all lines: code/guides/bring-your-own-sphinx.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,4 @@ While the `esbonio` language server is bundled as part of the extension, it does
4
4
5
5
This is because every Sphinx project is unique with its own set of dependencies and required extensions. In order to correctly understand your project `esbonio` needs to use the same Python environment that you use to build your documentation.
6
6
7
-
The Esbonio extension supports two mechanisms for selecting your Python environment.
8
-
9
-
1. If the official Python extension is available, by default Esbonio will attempt to use the same environment you have configured for your workspace.
10
-
2. Alternatively, you can use the `esbonio.sphinx.pythonCommand` setting to override this behavior.
7
+
You can tell Esbonio which environment to use by setting the `esbonio.sphinx.pythonCommand` option. See [this guide](https://docs.esbon.io/en/latest/lsp/howto/use-esbonio-with.html) for some examples
0 commit comments