Add to pyproject.toml :
Or for pure Pylance ( .vscode/settings.json ):
Look for an interpreter path that includes .cache/pypoetry or your project's local .venv folder 1.2.2 . pylance missing imports poetry hot
The code ran perfectly. The Poetry environment was pristine. poetry show listed the local core package. poetry run pytest passed with flying colors. But in VS Code, Pylance, the stoic serpent of static analysis, was convinced the import did not exist.
This is one of the most common friction points in Python development. The core issue is simple: (the VS Code Python language server) is looking at the system Python interpreter, while your code is running inside a specialized Poetry virtual environment . Add to pyproject
poetry config virtualenvs.in-project true poetry env remove # optional, then poetry install
The line was under from core.engine import HotReloader . poetry show listed the local core package
It was 1:30 AM. The demo was in 7.5 hours.
The blue squiggles remained. The code was gaslit by its own linter.
Poetry keeps your local environment clean by strictly isolating project dependencies. By default, it builds a dedicated virtual environment inside a centralized system cache folder: ~/Library/Caches/pypoetry/virtualenvs
,