Locrian
- 1,881
- 256
pbuk said:The problem is that in Windows there is no such thing as "yourenvfolder".
Sure there is!
Here's the exact code I would type to create and activate it in git bash:
Code:
python -m venv envs/physicsforum
source envs/physicsforum/Scripts/activate
The first line creates a "phsysicsforum" folder in my "envs" folder. Envs is where I keep all my environments; you can put yours somewhere else. You can even place it in your repo, though that's generally inadvisable. You might need to do so if you're leveraging lambda or other serverless tool.
The second line activates that folder in my path, just as you say needs to be done.
When I'm done with that environment, i can activate another one or type "deactivate" to return to defaults.
I keep an activate.env bash script in each of my repos that does the "source" command, so I don't have to type it in every time.