Skip to content

Broader search for locating pixi environment  #24042

@anthonykim1

Description

@anthonykim1

Apparently entering absolute path to pixi environment instead of relative to active workspace will cause "no interpreter" scenario for pixi environment from: #23975 (comment)

We could probably modify

// Usually the pixi environments are stored under `<projectDir>/.pixi/envs/<environment>/`. So,
or revisit logic for when user enters absolute interpreter path and somehow that leads to Python extension not being able to detect interpreter in that absolute path.

Inserting relative path seems to work fine. Perhaps we need to trim down when absolute path is given and convert it to relative path?

Context: #23975 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-environmentsFeatures relating to handling interpreter environmentsbugIssue identified by VS Code Team member as probable bugneeds PRReady to be worked on

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions