microsoft / microsoft/vscode-python-environments
Use the Prefix path for the environment when autofinding projects
- Dominant language
- TypeScript
- Stars
- 138
- Forks
- 62
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 35
Description
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.
_Originally posted by @karthiknadig in https://github.com/microsoft/vscode-python-environments/pull/405#discussion_r2087610280_
Contributor guide
Research direction
No file or test is named. Start by tracing the project autofinding entry point and how it selects the environment path; compare the current `.venv` behavior with the requested Prefix or sysPrefix path. Done means workspace discovery uses the environment's sysPrefix and ignores `pyproject.toml` and `setup.py` there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript
- Domain
- devtools, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100