pixi shell not activated due to read-only variable

amirhosseindavoody commented 2 weeks ago

Checks

[X] I have checked that this issue has not already been reported.
[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

pixi self-update
pixi shell

Issue description

I am using zsh on linux Suse 4.12.

I was working fine with pixi 0.23 version. After updating to 0.24.1 version when I activate the pixi shell I get the following message and the python environment does not get activated.

The read-only variable in the pixi generated shell script is this:

export _="/nfs/site/home/adavoody/.pixi/bin/pixi"

Expected behavior

The python should point to the python version in the working directory.

ruben-arts commented 2 weeks ago

I found the issue: https://github.com/prefix-dev/pixi/pull/1395/files#diff-f84977a6e7fdf8147b0d4b75f15a45112eff4507146389b1fb84e4647e0489c8R236

Here I add the full env vars set to the activation script. Which is not what you want in an already activated shell.

Looking for a fix.

amirhosseindavoody commented 2 weeks ago

@ruben-arts Thanks for closing this quickly.

prefix-dev / pixi