Option to specify project-wide jupyter:
kernel
#2850
Closed
pat-alt
started this conversation in
Feature Requests
Replies: 2 comments 2 replies
-
It should be possible to do something like this, and your document structure looks good to me. Feels like it's a bug on our side. I'll create an issue to track. |
Beta Was this translation helpful? Give feedback.
2 replies
-
Closing as completed and in favour of #2853. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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 where the kernel defaults to the default kerneljulia-1.6
for the document withoutjupyter
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.
Beta Was this translation helpful? Give feedback.
All reactions