You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Use the Prefix path for the environment when autofinding projects #406
Actually, we need to use the Prefix path for the environment. This is not always good enough. I think for now `.venv` is ok, but really we should use the sysPrefix path for environment for the workspace and ignore all `pyproject.toml` or `setup.py` from there.
When looking for projects, the extension currently finds files such as pyproject.toml or setup.py. However, those files can also exist inside a Python environment, as part of the installed packages.
The extension should ignore pyproject.toml and setup.py files under the environment's sysPrefix directory, not just under .venv directories.
This prevents the installed packages from producing false positives.
Activity
edvilme commentedon Sep 30, 2026
Proposed workflow
When looking for projects, the extension currently finds files such as pyproject.toml or setup.py. However, those files can also exist inside a Python environment, as part of the installed packages.
The extension should ignore pyproject.toml and setup.py files under the environment's
sysPrefixdirectory, not just under.venvdirectories.This prevents the installed packages from producing false positives.
Exclude selected environment sysPrefix from Auto Find project discove…
Auto Find: exclude markers inside each workspace folder's selected en…