quarto-dev / quarto-dev/quarto-cli
`jupyter`: warn when kernel apparently doesn't support inline expressions (was: Stata inline code error)
Open
@cscheid is already working on this.
Since Oct 7, 2024.
engines-jupyter
enhancement
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Bug description
My attempt to use Stata inline code results in an apparent Python error.
Steps to reproduce
Sample doc:
---
title: "Stata inline code"
format: html
jupyter: nbstata
---
```{stata}
disp 3
```
Testing inline `{stata} disp 3`.
I attempt to create a preview from within VSCode and get the following terminal output:
Starting nbstata kernel...Done
Executing 'stata-inline.quarto_ipynb'
Cell 1/1: ''...Done
ERROR:
'NoneType' object has no attribute 'get'
Expected behavior
No response
Actual behavior
No response
Your environment
- IDE VSCode 1.94.0 (with Quarto extension v1.115.0)
- OS: Windows 11
Quarto check output
Quarto 1.5.57
[>] Checking versions of quarto binary dependencies...
Pandoc version 3.2.0: OK
Dart Sass version 1.70.0: OK
Deno version 1.41.0: OK
Typst version 0.11.0: OK
[>] Checking versions of quarto dependencies......OK
[>] Checking Quarto installation......OK
Version: 1.5.57
Path: C:\Users\tjhuegerich\AppData\Local\Programs\Quarto\bin
CodePage: 1252
[>] Checking tools....................OK
TinyTeX: (not installed)
Chromium: (not installed)
[>] Checking LaTeX....................OK
Tex: (not detected)
[>] Checking basic markdown render....OK
[>] Checking Python 3 installation....OK
Version: 3.10.12 (Conda)
Path: C:/Users/tjhuegerich/AppData/Local/anaconda3/envs/nbstata_demo/python.exe
Jupyter: 5.3.1
Kernels: nbstata, python3
[>] Checking Jupyter engine render....OK
[>] Checking R installation...........(None)
Unable to locate an installed version of R.
Install R from https://cloud.r-project.org/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.