quarto-dev / quarto-dev/quarto

Consider prompt to `pip install jupyter`

Open
#639 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

vscode
Dominant language
TypeScript
Stars
645
Forks
62
Avg merge
17h 42m
Merged PRs (30d)
13

Description

One thing I have tripped over many times when using a Python .qmd file is that I need the jupyter Python package installed to render it. I do see documentation at places like this:

https://quarto.org/docs/get-started/hello/vscode.html#basic-workflow

But it's actually not clear IMO that you need the jupyter package just to make Quarto work at all.

One idea to help here would be to detect that jupyter is not installed in the active/current Python and prompt to install it. We do this in the Positron Python extension for ipykernel, which is needed for the console to work.

See https://github.com/posit-dev/positron/blob/01b4b65925a4990c4048d6bbea9cfd2b2ae5bcc4/extensions/positron-python/src/client/positron/session.ts#L241-L245

It's possible that we build in some check here in the Quarto extension that then calls to Positron to do the check, since we have all that infrastructure already set up and I don't believe this extension does.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Quarto extension's existing infrastructure for checking the active Python environment, then compare it with Positron's extensions/positron-python/src/client/positron/session.ts at lines 241-245. Determine how the extension could coordinate with Positron to detect a missing jupyter package and prompt for installation; done means a Python .qmd workflow clearly prompts when jupyter is unavailable.

Written by the indexing model from the issue text.

Assessment

Tech stack
jupyter, python, typescript
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.