Re:We're Leaving Kubernetes
by fastasucan on Monday November 04, 2024 @04:36PM
(#42046228)
Weird, in my experience vscode makes it very clear by making you explicitly choose a .venv when running or debugging.
When it comes to opening a new terminal, you would have the exact same problem by... running commands in a terminal, cant see how vscode related that is.
I watched it last week. With 4 (I hope junior) Devs in a "pair programming" session that forced me to figure out how VSCode does virtual envs, and still I had to tell them like 3 times "stop opening a damn new terminal, it's obviously not setup with our python version, run the command inside the one that has the virtual env activated".