If you are a Python developer using Visual Studio Code, you have likely experienced a unique flavor of frustration: your terminal runs the code perfectly, poetry show --tree lists all your dependencies, yet your editor is littered with angry yellow squiggles. Hovering over the import reveals the dreaded message:
poetry env info --path
# Check if Poetry is installed poetry --version
"python.defaultInterpreterPath": "/home/user/.cache/pypoetry/virtualenvs/my-project-abc123-py3.9/bin/python" pylance missing imports poetry link
"python.analysis.extraPaths": ["./src", "./myproject"]
Configure the base path using python.venvPath and point python.venvFolders to match your specific environment name:
: Run poetry run python -c "import your_missing_package" in your terminal. If this command throws an error, the package is missing from your pyproject.toml file or failed to install. Run poetry install again. If you are a Python developer using Visual
切换后建议执行以下操作确保 Pylance 识别新环境：
| 场景 | 症状 | 解决方案 | |------|------|---------| | 标准 Poetry 项目 | Pylance 无法解析任何依赖 | 选择正确解释器即可解决 | | 可编辑依赖 ( develop=true ) | 本地开发的包无法导入 | 使用 extraPaths 指向依赖源码目录 | | Jupyter Notebook | .ipynb 文件报错 .py 正常 | 保存文件后重新加载窗口 | | Monorepo 多项目 | 跨项目导入失败 | 使用 extraPaths 或 pyrightconfig.json 配置路径 |
If you have tried the methods above and still see missing import warnings, try these advanced troubleshooting steps: 1. Clear the Pylance Cache and Restart Sometimes Pylance holds onto stale cache data. Open the Command Palette ( Ctrl/Cmd + Shift + P ). Run poetry install again
poetry check
Pylance looks at your workspace folder, doesn't see a venv folder, and assumes you are working in a global environment—which has none of your Poetry packages. Hence:
If you’ve added a new package but not run poetry install , Pylance won’t see it. Always run:
Ensure your dependencies actually installed correctly inside the environment. Run poetry run pip list to double-check that the missing module is present in the active Poetry environment. If it is missing, run poetry add . 3. Check for Multi-Root Workspaces