Pylance Missing Imports Poetry Hot

If you have a client/ and server/ folder, each with its own poetry.lock:

Fix: You need a multi-root workspace. Open the root folder, then File -> Add Folder to Workspace. Each child folder will need its own interpreter selection. Use the .vscode/settings.json in the workspace root to map each subfolder:

    "settings": 
        "folders": [
"path": "client",
                "settings": 
                    "python.defaultInterpreterPath": "client/.venv/bin/python"
,
"path": "server",
                "settings": 
                    "python.defaultInterpreterPath": "server/.venv/bin/python"
]

If you are importing your own local modules (e.g., from src import mymodule) and Pylance marks them as missing even after selecting the correct interpreter, you may need to explicitly tell Pylance where to look. pylance missing imports poetry hot

  "extraPaths": ["./src"],
  "typeCheckingMode": "basic"

(Replace "./src" with the actual folder name where your code resides).

If you cannot change your virtual environment location (e.g., a team standard), you can manually tell Pylance where to look. Pylance is built on Pyright, so we can configure it via pyrightconfig.json. If you have a client/ and server/ folder,

Create a file in your project root called pyrightconfig.json:

  "venvPath": "/path/to/your/global/poetry/venvs",
  "venv": "your-project-name-xyz-py3.9",
  "extraPaths": [
    "."
  ]

How to get the values:

Reload VS Code. This forces Pylance to inspect that specific environment.

To make it bulletproof, create a workspace setting. In your project root, create a .vscode folder, then a settings.json file: If you are importing your own local modules (e

    "python.defaultInterpreterPath": "$workspaceFolder/.venv/bin/python",
    "python.terminal.activateEnvironment": true,
    "python.analysis.extraPaths": [
        "$workspaceFolder/src"
    ]

Did you try all the above and Pylance still gives you the yellow squiggle? Here are the "hot" edge cases: