Activation with powershell scripts opens file instead of executing it

[melund]

Checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

On Windnows add an activation section to pixi.toml

[activation]
scripts = ["setup.ps1"]

Create a setup.ps1 with any content.

$env:MY_ENV_VAR="Hello World"

Now activate the shell:

PS> pixi shell

This opens the setup.ps1 file in NotePad, instead of executing it. Shell activation hangs until the file is closed.

Issue description

On Windows activations using powershell scripts doesn't work. They open the script file in Notepad instead of executing it.

Using *.bat files works fine as workaround.

Expected behavior

The powershell script should run.

[ruben-arts]

The problem is that we need to run the activation scripts using the system shell interpreters so as of right now we use the default shells so we always know it will be available. This is cmd.exe on windows and bash on Unix. This makes it that it can't run the .ps1 files.

For now I'll update the documentation to explain this behavior. Would that be enough for you?

[melund]

For now I'll update the documentation to explain this behavior. Would that be enough for you?

Yes . Of course :) Documentation just hinted that it had or was supposed to work.

[ruben-arts]

Oops haha, that was a mistake!

[ruben-arts]

Fixed in : #563