Bug description
In the _quarto.yml file, setting engine: knitr or any variants (jupyter: python3, etc) should apply as the default for any files unless modified in the subsequent file's YAML.
On M1 Pro Mac running MacOS Monteray.
Using RStudio Version 2022.12.0-preview+303 (2022.12.0-preview+303)
Quarto v1.2.242
Reprex:
- Create a project
quarto create-project test-engine
- Set
engine: knitr in the _quarto.yml
project:
type: website
website:
title: "test-engine"
navbar:
left:
- href: index.qmd
text: Home
- about.qmd
format:
html:
theme: cosmo
css: styles.css
toc: true
engine: knitr #<- this is the change
- Change a chunk in the
index.qmd to python:
quarto render
The render of index.qmd is executed within a Jupyter kernel instead of knitr + reticulate even with the engine: knitr set at global/_quarto.yml level.
The correct behavior would be to use knitr since that is set at the global level.
Checklist
Bug description
In the
_quarto.ymlfile, settingengine: knitror any variants (jupyter: python3, etc) should apply as the default for any files unless modified in the subsequent file's YAML.On M1 Pro Mac running MacOS Monteray.
Using RStudio Version 2022.12.0-preview+303 (2022.12.0-preview+303)
Quarto v1.2.242
Reprex:
engine: knitrin the_quarto.ymlindex.qmdtopython:quarto renderThe render of
index.qmdis executed within a Jupyter kernel instead ofknitr+reticulateeven with theengine: knitrset at global/_quarto.ymllevel.The correct behavior would be to use
knitrsince that is set at the global level.Checklist