### Discussed in https://github.com/quarto-dev/quarto-cli/discussions/2850

<div type='discussions-op-text'>

<sup>Originally posted by **pat-alt** October 14, 2022</sup>
Currently Jupyter kernels need to be specified on a per-document basis. In other words, specifying the Jupyter kernel in `_quarto.yml` or `_metadata.yml` has no effect: see this [example](https://github.com/pat-alt/quarto-example/tree/main/project-wide-jupyter-kernel) where the kernel defaults to the default kernel `julia-1.6` for the [document](https://github.com/pat-alt/quarto-example/blob/main/project-wide-jupyter-kernel/doc-without-specified-kernel.md) without `jupyter` explicitly declared in the YAML header. Is this a deliberate design choice? Is there anything that speaks against specifying kernels for multiple documents?

**Background**: I'm using Quarto to document my Julia packages. Being able to to control the Julia version for all my docs at once would give me a way to check locally if all code chunks execute successfully for that version. </div>
cscheid
2022-10-14T14:42:34Z
cscheid
bug jupyter
v1.2
closed
Option to specify project-wide `jupyter:` kernel
https://github.com/quarto-dev/quarto-cli/issues/2853