Stop injecting Python interpreter and improve Sphinx Process tree #881
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In an attempt to simplify the first time setup (#733) this PR stops the VSCode extension from automatically injecting the currently active Python interpreter into the configuration sent to the server.
This will force users to have to set the
esbonio.sphinx.pythonCommand
setting, which while annoying to those who were relying on the previous behaviour I think will be an improvement in the long run.hatch
orpoetry
pyproject.toml
file, further simplifying the setup for the Nth user to a project.This PR also includes some updates to the Sphinx Process tree!
Each Sphinx process can be further expanded to include