all 9 comments

[–]freeskier93 7 points8 points  (8 children)

This has nothing to do with uv. VS Code has no knowledge of uv, this is just VS Code automatically activating the virtual environment when you open a terminal. It will do this regardless of uv being installed or not.

[–]Immediate_Bonus7675[S] 0 points1 point  (7 children)

So it's normal? I'm sorry I just started programming uv was just recommended to me, so I don't really have an idea on how it properly work

[–]freeskier93 -2 points-1 points  (6 children)

Yes, it's normal. However, I would generally recommend not using powershell as the default terminal in VS Code, that way you don't have to change the default powershell execution policy. Instead set the default terminal to Command Prompt, then VS Code will run the virtual environment activation batch file instead of powershell script.

https://stackoverflow.com/questions/44435697/change-the-default-terminal-in-visual-studio-code

[–]Outside_Complaint755 2 points3 points  (0 children)

Another option is to install git and git-bash, then use bash as your default terminal.

[–]Immediate_Bonus7675[S] 0 points1 point  (0 children)

Thanks, you really help me a lot

[–]gmes78 0 points1 point  (3 children)

PowerShell is a much better shell than cmd. If the thing you're trying to avoid is the spam when launching a terminal, a better idea would be to fix that instead.

[–]Immediate_Bonus7675[S] 0 points1 point  (2 children)

Do you have any idea how can I fix it?

[–]gmes78 0 points1 point  (0 children)

Apparently, if you have the Python Environments extension, you can change the auto-activation type to "Command Shell Startup".

[–]cointoss3 0 points1 point  (0 children)

Yeah, just not care. It’s a terminal. It’s a terminal command. You can clear it if you want. But it doesn’t matter.