-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Xonsh adds unwanted entries to PATH #248978
Comments
I think the recommended way to do this is to add an override to xonsh.
See #240246 |
That's a help but if I launch a nested xonsh by running I've removed these unwanted programs.xonsh.enable = true;
programs.xonsh.package = pkgs.xonsh.override {
xonsh-unwrapped = pkgs.xonsh-unwrapped.overridePythonAttrs (
old: {dontWrapPythonPrograms = true;}
);
}; Everything works fine so far. |
@SamLukeYes since your PR was reverted is this issue still fixed? ETA: looks ok but if anyone still has |
To make it clear, |
Oops, it seems we have re-introduced this issue in #314728 |
Describe the bug
Using xonsh in a
nix-shell
environment can override the Python interpreter, which is a problem if the environment is supposed to use a specific one.Steps To Reproduce
Then create
shell.nix
containingThen inside xonsh, a different Python interpreter is used:
Expected behavior
Running xonsh should not modify the
PATH
such that a differentpython
executable is used. In the above, when we runpython
we should get therequests
library.Workarounds
Running
$PATH.pop(0)
removes the problematic PATH entry but this is pretty hacky.Notify maintainers
@vrthra
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.The text was updated successfully, but these errors were encountered: