PYTHONPATH=${workspaceFolder}/src VS Code's Python extension automatically loads .env files. Add a script in your pyproject.toml to remind or automate:
Look for an interpreter path that contains .venv , poetry , or your project name. If you see ./.venv/bin/python , select it. If you see ~/Library/Caches/pypoetry/virtualenvs/... , select it. pylance missing imports poetry hot
[tool.poetry.scripts] post-install = "scripts:notify_vscode" And a simple Python script that touches .vscode/settings.json to force a reload. You might see advice online: "Just install the package globally." Never do this. It pollutes your system Python and defeats the purpose of Poetry. If you see ~/Library/Caches/pypoetry/virtualenvs/
This article is the definitive guide to understanding why this happens and, more importantly, how to fix it permanently. Before typing random commands, it’s crucial to understand why this breakage occurs. Pylance is a static type checker. It needs to know the exact Python interpreter and site-packages path to validate your imports. Poetry, by default, is "non-intrusive." It creates virtual environments in a cache directory (e.g., ~/Library/Caches/pypoetry/virtualenvs/ on macOS or %APPDATA%\pypoetry\virtualenvs on Windows). You might see advice online: "Just install the
Introduction: The Perfect Storm of Modern Python Development You’ve embraced modern Python development. You use Poetry for dependency management and virtual environments because you’re tired of the requirements.txt chaos. You use VS Code with Pylance because you want blazing-fast type checking and autocompletion.