Currently you must do the following to execute cells with Quarto.  You either have to:

1. pass the `--execute` flag to `quarto preview` or `quarto render`
2. Set the `enabled: true` flag as specified [here](https://quarto.org/docs/computations/python.html#workflow)

However, this is confusing for many reasons

1.  `enabled` is not documented here under execution options https://quarto.org/docs/reference/formats/ipynb.html#execution
2. The [documentation suggests](https://quarto.org/docs/reference/cells/cells-jupyter.html#code-output) that setting `eval: true` should make quarto execute that cell (or notebook, if placed in the front matter).  However, this is not the case.  You have to additionally take the steps in number 1. 
3. If you have a project where some notebooks are executed but others are not, this leads to **Quarto deleting all cell outputs** in notebooks where `eval: false` on cells (or for the whole notebook if in front matter).   However, I don't think this is desirable for notebooks, because you may have long-running computations that generate some output that you don't want get clobbered by Quarto - and it looks like there isn't a way to "protect" those cells or notebooks?

cc: @jjallaire @seem @cderv @mcanouil 

BTW I'm on `1.3.333`

cderv
2023-05-01T17:50:56Z
hamelsmu
documentation jupyter
open
Jupyter Execution is Confusing And Possibly Has A Bug
https://github.com/quarto-dev/quarto-cli/issues/5376