Add locator for pixi environments

[baszalmstra]

Closes #22978

This adds a locator implementation that properly detects Pixi environments. Pixi environments are essentially conda environments but placed in a specific directory inside the project/workspace. This PR properly detects these and does not do much else. This would unblock a lot of pixi users.

I would prefer to use a custom pixi plugin but since the contribution endpoints are not available yet I think this is the next best thing.

Before I put more effort into tests I just want to verify that this approach is valid. Let me know what you think! :)

[baszalmstra]

@microsoft-github-policy-service agree company="Prefix.dev GmbH"

[karrtikr]

Thanks for the PR, please create an issue corresponding to the same, we hope to get to this shortly.

[baszalmstra]

Thanks for the PR, please create an issue corresponding to the same, we hope to get to this shortly.

Ofc, see #22978

[baszalmstra]

I took the time to also add tests. These are based on the ones from hatch and poetry.

[karrtikr]

Thanks for the work, I'm happy with it overall. If you could also work on the test plan item to verify it, that would be great. for eg. #21298, #21102.

See #22779 (comment) for similar ask from another tool, feel free to let me know if there's any questions,

[baszalmstra]

Looking at #22779 (comment) this PR currently only adds discovery, (I would like to work on the rest after this).

Would a test-plan like this suffice?

Requirements:

• Have a working pixi installation (>0.15.2), installation instructions can be found here: https://pixi.sh/ .

Verification:

• Open a new empty workspace folder.
• Open a terminal in the workspace and run the following commands to initialize a pixi project with a python interpreter:

  pixi init . 
  pixi add python
  

• Add an script.py file to the root of the workspace and open it (the contents doesnt matter).
• Verify that a default interpreter has been selected that points to python interpreter in the .pixi\envs directory of the workspace. Its type should be Pixi.

[pavelzw]

@baszalmstra maybe also add multi envs to the test plan?

[karrtikr]

@pavelzw That sounds fine for discovery, I think this PR might also cover additional scenarios, as pixi environments are essential conda under the hood:

Activation and Execution:

#22779 (comment)

Installation:

• Select a pixi environment
• Open a new terminal
• Install something using pip
• Make sure it is installed

If this doesn't work, we might need to add a pixiInstaller.ts similar to

vscode-python/src/client/common/installer/condaInstaller.ts

Line 19 in 358635d

export class CondaInstaller extends ModuleInstaller {

[karrtikr]

Merge conflicts ⚔️ Here's an example test plan item for the Discovery & Activation part: #23088. Please @ me once this is done, unsubscribing for now.

[martinhulin]

Looking at #22779 (comment) this PR currently only adds discovery, (I would like to work on the rest after this).

Would a test-plan like this suffice?

Requirements:

• Have a working pixi installation (>0.15.2), installation instructions can be found here: https://pixi.sh/ .

Verification:

• Open a new empty workspace folder.
• Open a terminal in the workspace and run the following commands to initialize a pixi project with a python interpreter:

  pixi init . 
  pixi add python
  

• Add an script.py file to the root of the workspace and open it (the contents doesnt matter).
• Verify that a default interpreter has been selected that points to python interpreter in the .pixi\envs directory of the workspace. Its type should be Pixi.

Will this also work for R?

[baszalmstra]

I have added implementations of activation, a module installer, and execution. Will add a test plan one of these days!

[pavelzw]

@karrtikr @karthiknadig whats the current state of this PR? I would love to get this available in vscode 😍

[karthiknadig]

@baszalmstra Is this ready for review?

[baszalmstra]

Sorry for leaving this for so long. I am on a holiday but will be back next week.

Im quite happy with the functionality provided by this PR. I think the biggest thing missing is the test plan. Also some unit tests might still be required, I could definitely use some help with those.