quarto-dev / quarto-dev/quarto
Pyright static analysis doesn't propagate fully to Python Quarto cell
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 645
- Forks
- 62
- Avg merge
- 17h 42m
- Merged PRs (30d)
- 13
Description
Bug description
Not all of Pyright's static code analysis propagates to Quarto Python cells. In particular, we do not get warnings for undefined variables. This seems to not happen in Python files themselves. In the example below I would expect the same error of an undefined variable as I see in the Python file.
vscode extension version: 1.123.0
Positron Version: 2025.06.0 (Universal) build 167
Code - OSS Version: 1.100.0
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Reproduce the example in a Quarto Python cell and compare Pyright diagnostics with the equivalent Python file. Trace the Quarto or Positron integration used with the VS Code extension and verify whether undefined-variable warnings propagate to the cell; done means both surfaces report the same warning.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100