microsoft / microsoft/vscode-python-environments
The thing hardly works and breaks everything
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 138
- Forks
- 62
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 35
Description
## Environment data
- Python Environments extension version: XXX
- Python extension (`ms-python.python`) version: XXX
- VS Code version (Help → About): XXX
- OS and version: XXX
- Python version (& distribution if applicable, e.g. Anaconda): XXX
- Environment manager in use (`venv` / `conda` / `pyenv` / `poetry` / `pipenv` / `system` / `uv` / other): XXX
- Shell (bash / zsh / fish / pwsh / cmd / other): XXX
- Remote / container scenario (none / WSL / SSH Remote / Dev Container / Codespaces): XXX
- Workspace type (single folder / multi-root / mono-repo): XXX
- Is this a regression? If yes, last known working extension version: XXX
## Repro Steps
1. XXX
## Expected behavior
XXX
## Actual behavior
XXX
## Logs
```
XXX
```
## Additional context
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is identified. First collect the requested extension, Python, VS Code, OS, environment-manager, shell, workspace, and remote details, then provide minimal reproduction steps, expected and actual behavior, and trace logs from the Python Environments output channel. Done means the failure is reproducible and scoped enough to identify an implementation area.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100