quarto-dev / quarto-dev/quarto-cli
[EPIC] Differences on generated Markdown between knitr and jupyter engine
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
This issue is here to list the differences we observed in our journey between what is output by Jupyter engine, and by knitr engine.
At the end, quarto processing should be quite the same no matter which engine did the computations evaluation, but currently the output can be quite different, and thus our processing becomes quite complex.
Overtime, we should aim to close the gap between the two
-
Label on cells is passed through on Jupyter not knitr
-
output: asisdifferences
Contributor guide
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
Start by reviewing linked issues #7665 and #7607, then compare the listed differences between the Jupyter and knitr engines. This is an epic rather than a self-contained task; done means the engine-output discrepancies are addressed or clearly tracked as separate follow-up work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter, markdown
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100