[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.
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: pylance missing imports poetry hot
By setting virtualenvs.in-project true , configuring your .vscode/settings.json , and understanding how to manually select the interpreter, you transform this sporadic nightmare into a reliable, automated workflow. Now, look in your project folder
{ "settings": { "folders": [ { "path": "client", "settings": { "python.defaultInterpreterPath": "client/.venv/bin/python" } }, { "path": "server", "settings": { "python.defaultInterpreterPath": "server/.venv/bin/python" } } ] } } Some developers use Conda for Python versions and Poetry for packages. This creates a nested environment confusion. To make it bulletproof, create a workspace setting