Okay so I wiped the .venv that VSCode made again and this time ran the venv creation using python3 -m venv venv
. It’s working with command line now but not within VSCode (running into the same issue that I had before but in reverse, so VSCode isn’t recognizing pip or other installed modules like markdown that I added in command line).
This is starting to feel like maybe a difference in how VSCode handles the virtual environment vs the command line. When I create the venv in one it breaks the other
Edit: Yeah idk what VSCode is up to. I uninstalled, remade the venv with Konsole, and installed PyCharm instead. Commands through Konsole and the PyCharm terminal are all working as expected now.
Thank you for the help!
I’m a slut for potatoes. If you don’t soak them in oil, butter, or cheese they’re about a kcal/gram. I like to nuke one and just add salt