[tool.poetry] name = "myproject" packages = [{include = "myproject", from = "src"}] Then, update your settings.json as shown above with python.analysis.extraPaths . If you have a client/ and server/ folder, each with its own poetry.lock :
If you don’t see the Poetry environment at all, click Enter interpreter path and manually paste the result of this command: pylance missing imports poetry hot
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: Each child folder will need its own interpreter selection
You are experiencing the "hot" pain point of the modern Python stack: VS Code and Pylance will auto-detect it without
Ensure your pyproject.toml includes your project package correctly:
Now, look in your project folder. You will see a .venv directory. VS Code and Pylance will auto-detect it without any manual intervention. To make it bulletproof, create a workspace setting. In your project root, create a .vscode folder, then a settings.json file: