Skip to content

Extension breaks python envy and associated use-case #661

@alita-moore

Description

@alita-moore

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 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.

Metadata

Metadata

Assignees

Labels

bugIssue identified by VS Code Team member as probable bugneeds proposal

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions