microsoft / microsoft/vscode-python-environments
Extension breaks python envy and associated use-case
@eleanorjboyd is already working on this.
Since Jul 28, 2025.
- Dominant language
- TypeScript
- Stars
- 138
- Forks
- 62
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 35
Description
I have a monorepo where i have independent pyproject.toml in project directories e.g.
- pyproject.toml
- libs
-- package
--- pyproject.toml
where I have it save the python environments in a local .venv like so
- .venv
- pyproject.toml
- libs
-- package
--- .venv
--- pyproject.toml
I use an extension called [python envy](https://marketplace.visualstudio.com/items?itemName=teticio.python-envy) and this allows me to now have separate projects that import each other using poetry development dependencies. python envy naturally switches between interpreters as you navigate the project.
This extension appears to completely break this use-case and extension.
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.
Assessment
This issue has not been assessed yet.