microsoft / microsoft/vscode-python-environments
allow usage of non-global uv executable
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 138
- Forks
- 62
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 35
Description
we currently look for uv on PATH, but we don't search the current workspace for it. This would be a feature request to **search in the current workspace for uv.**
in this example the `uv.exe` is located at `{workspaceFolder}/.pyprojectx/main/uv.exe`
https://github.com/microsoft/vscode-python-environments/issues/621
tagging @DetachHead
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
Start by locating the existing extension entry point that searches PATH for the uv executable, then review the linked issue for context. There are no file or test paths named; done means the current workspace location, including .pyprojectx/main/uv.exe, is searched for uv.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100