Comment on Using source command for virtual Python environment

<- View Parent
ArmoredThirteen@lemmy.zip ⁨2⁩ ⁨weeks⁩ ago

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

source
Sort:hotnewtop