quarto-dev / quarto-dev/quarto
Feature request: Quarto VSCode extension to be able to select conda environment for execution
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
When running Jupyter notebooks on VSCode, I can select kernels based on conda environments. When running Quarto qmd files on VSCode, I'm bound to the rpath set for the project (which normally doesn't work that well with conda envs). It would be great if the quarto VSCode extension would present to the user, per .qmd file, the ability to pick a conda environment. That would put .qmd and jupyter notebooks at the same level of usability dependencies wise (currently I'm doing all my quarto from jupyter because debugging cells in .qmd its hard when you cannot pick the environment for that .qmd file).
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the Quarto VSCode extension and .qmd execution, but no files or tests. Start by locating the extension entry point for running .qmd files and compare it with VS Code's conda-based notebook kernel selection. Done means a user can choose a conda environment per .qmd file and use it for execution and debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100