Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broader search for locating pixi environment #24042

Open
anthonykim1 opened this issue Sep 3, 2024 · 0 comments
Open

Broader search for locating pixi environment #24042

anthonykim1 opened this issue Sep 3, 2024 · 0 comments
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug needs PR Ready to be worked on

Comments

@anthonykim1
Copy link

anthonykim1 commented Sep 3, 2024

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)

@anthonykim1 anthonykim1 added feature-request Request for new features or functionality area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug and removed feature-request Request for new features or functionality labels Sep 3, 2024
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Sep 3, 2024
@karthiknadig karthiknadig added needs PR Ready to be worked on and removed triage-needed Needs assignment to the proper sub-team labels Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-environments Features relating to handling interpreter environments bug Issue identified by VS Code Team member as probable bug needs PR Ready to be worked on
Projects
None yet
Development

No branches or pull requests

2 participants