How do I keep lightbox groups when running quarto convert on python based qmd files?
#14392
Replies: 3 comments 6 replies
-
|
Seems like a bug or an oversight. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @mcanouil, I have considered both the Additionally, I prefer to write in quarto source mode as I find it is easier to edit and audit text/code as compared to |
Beta Was this translation helpful? Give feedback.
-
|
When I convert to Jupyter Notebook, the ...
{
"cell_type": "code",
"metadata": {
"lightbox": {
"group": "figs"
}
},
"source": [
"#| label: fig-sine\n",
"#| fig-cap: Sine plot\n",
"\n",
"import matplotlib.pyplot as plt\n",
"import numpy as np\n",
"\n",
"x = np.linspace(0, 10, 100)\n",
"plt.figure()\n",
"plt.plot(x, np.sin(x))\n",
"plt.title(\"Sine\")\n",
"plt.show()"
],
"execution_count": null,
"outputs": []
}
...If you convert back to qmd from ipynb, you'll see the lightbox coming back. In the case of R code cells, you've set The behaviour to split options between source and metadata is by design. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Description
Hello everyone,
I have noticed over the last few months that when I run
quarto convert some_python.qmdlightbox groups do not carry over to the resultingsome_python.ipynb.Here's a simple reproducible example:
However, when I do the same for an
R-basedqmd, lightbox groups always carry over. Here's example:Why do I need this? Why not just work in
qmdfiles.I often run exploratory analyses on large datasets, and then render these to a quarto website that serves as my lab notebook. Due to dataset size, each exploratory analysis can run hours at a time. Jupyter notebooks are preferred because when I render, quarto does not rerun the whole notebook.
OS and package versions
Beta Was this translation helpful? Give feedback.
All reactions