quarto-dev / quarto-dev/quarto

Pyrefly does not resolve installed modules against the workspace venv in cell diagnostic vdocs

Open
#1,014 4 comments 0 reactions 1 assignee View on GitHub

@seeM is already working on this.

Since Jun 17, 2026.

bug vscode
Dominant language
TypeScript
Stars
645
Forks
62
Avg merge
17h 42m
Merged PRs (30d)
13

Description

A user ran into this issue with cell diagnostics.

Sharing a repro in case it's useful:

  1. Positron with a project that has a .venv containing dependencies not installed in the system/global Python (e.g., polars).
  2. System Python on PATH = Homebrew (here python@3.14), without polars.
  3. Open a .qmd with a cell that does import polars.

What I see: Pyrefly flags "Cannot find module 'polars'" and appears to resolve against the global Python rather than the project .venv.
python.defaultInterpreterPath, the interpreter picker, and QUARTO_PYTHON didn't change it.
Positron's own Pyrefly resolves the .venv fine, seems specific to the cell-diagnostics path.

Downgrading to 1.132.0 fixes it.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.