trying to make python work is such an adventure lol, virtual environments are a nightmare of usability failures, most importantly just because you have to remember to actually select the right one. and then you take that and throw vscode over the top and it's full clown mode, as soon as it's even slightly broken you get incorrect suggestions from vscode and from python to install stuff into the global install. (which then silently fail because i disabled installation without an active venv)
You'd think like typing "virtual environment" or "python virtual" or "python venv" or whatever into the vs code prompt would give you a command like "choose virtual environment" but it doesn't. They seem to randomly switch between terminology. And the default for everything is still yolo install into the user scope.
Edited 8d ago