Add experimental VS Code (code) runtime to juv run
#62
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR adds a `code` runtime option to `juv run`, allowing VS Code to be launched in a way similar to other Jupyter runtimes. The approach uses the behavior of the `code` CLI, which inherits the environment it was run in. A script is created using the inline metadata so that running `code <notebook.ipynb>` ensures a virtual environment is available in the VS Code session with the necessary dependencies. Ideally, we'd have a VS Code extension to dynamically create and register virtual environments for better discoverability. This implementation goes the other way by enabling basic support via the CLI. However, the user must manually select the virtual environment from VS Code's dropdown, where it appears with an obscure, temporary name (derived from the hashed environment created by `uv`).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a
coderuntime option tojuv run, allowing VS Code to be launched in a way similar to other Jupyter runtimes.The approach uses the behavior of the
codeCLI, which inherits the environment it was run in.A script is created using the inline metadata so that running
code <notebook.ipynb>ensures a virtual environment is available in the VS Code session with the necessary dependencies.Ideally, we'd have a VS Code extension to dynamically create and register virtual environments for better discoverability. This implementation goes the other way by enabling basic support via the CLI. However, the user must manually select the virtual environment from VS Code's dropdown, where it appears with an obscure, temporary name (derived from the hashed environment created by
uv).