Open maurosilber opened 3 weeks ago
I'm having the same issue. I have to specify which environment the task uses if I try to run it when I have my "tests" environment activated in VSCode.
This issue doesn't occur if I downgrade to 0.33.0 but reappears as soon as I go up to 0.34.0 and on.
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
Here is a simple
pixi.toml
to reproduce this issue:And a series of commands and their outputs with
pixi == 0.35
:Issue description
This might not be a bug, but I cannot run a task from a given environment without explicitly adding
-e <env>
if I'm within the shell of another environment. In my project, I havelint
environment with alint
task that I used to run withpixi run lint
, since it is the only environment defining a task with that name. But the Python extension in VSCode activates another environment automatically in its terminal. Maybe I should just prevent the VSCode extension from activating an environment in the terminal.Expected behavior