posit-dev / posit-dev/positron
python: investigate opt-in usage of the upstream environments extension
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 4.3k
- Forks
- 184
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 195
Description
As a followup to https://github.com/posit-dev/positron/issues/11405, investigate what short- and long-term work it would take to fork https://github.com/microsoft/vscode-python-environments, keep it disabled by default, and choose to opt in to using its API when we explicitly want to for Positron features like the environments pane (https://github.com/posit-dev/positron/issues/11214).
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 reviewing the follow-up issue 11405, the upstream microsoft/vscode-python-environments project, and the environments pane issue 11214. Document the short- and long-term work needed to fork the extension, keep it disabled by default, and opt in to its API for Positron features; done means the integration approach and scope are clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100