Selecting a uv `.venv/bin/python` as active interpreter doesn't enable IDE feature

[konstin]

Hi, I'm writing this to upstream a uv issue report (astral-sh/uv#9637). I hope this isn't a duplicate, I couldn't find any existing upstream report, and sorry for misusing the feature request page, it didn't fit the usual bug report flow. This report has some untypical characteristics:

• A lot of users seem to experience it (50 +1's on the uv issue)
• The uv team can't reproduce it
• There is a workaround: Selecting .venv/bin/python as an active interpreter in VSCode doesn't enable IDE features astral-sh/uv#9637 (comment)

The users report that when selecting a venv from python -m venv as active interpreter, VS code reports it has full IDE support. When they do the same with the uv created venv, VS Code does not activate IDE features such as Intellisense, type hints and Mypy. The workaround is to enter the absolute path to the venv instead, which seems to make VS Code recognize the extension.

Does the VS Code Python team know what may cause, and what we could do on the uv or VS code side to fix this? We're interested in a great VS Code experience for our users, but we're unfortunately out of ideas on the issue.

CC @karthiknadig

[karthiknadig]

@konstin Do you see the same problem when using (https://marketplace.visualstudio.com/items?itemName=ms-python.vscode-python-envs) extension?

Install that extension and reload VS Code. That will cause python extension to replace its features with the new extension. That will soon be replacing all the environment features in python extension.

[Benoss]

This is working for me with the preview extension!