How To Create & Activate A Virtual Environment In Visual Studio Code (Python 3.12) 

I will write this down for the next tutorial!

I thought the same thing, just tried `exit` and it worked for me

in vs code you can create and activate virtual environment using command panel too

In Windows Activate goes with capital "A" -> .venv\Scripts\Activate

I have just done it yesterday. Depending on which shell you use it might be correct. For example in Powershell you need to ".\.venv\Scripts\Activate.ps1" and also enable scripts in powershell. But scripts in PS is another topic

.\.venv\Scripts\Activate

You might want to run the windows command to check the .venv directory since I believe that "python -m venv .venv" and "py -m venv .venv" produce different folder structures in .venv

I never explored anything else other than the built-in; any particular reason your prefer pipenv?

@@Indently Pipenv is: 1. More automatic, one command (`pipenv install`) creates virtual environment and file with dependices 2. Just type `pipenv shell` to activate environment 3. New module installation adds depedicies automatically 4. Type just `exit` to deactivate environment 5. If You want clone virtual environment on other computer just paste depedicies file (`Pipenv.lock`) and type `pipenv sync`. 6. To remove environment just type `pipenv --rm` 7. You can create a requirements.txt file for venv It is worth trying `pipenv`, at most it will not appeal to you.

Thanks for sharing, I will take a dive into it!

I know that the "." makes the folder invisible on Mac OS, but to be honest it's just what I've been doing since I started programming in Python. I would love to hear from someone else whether there's any benefit of doing that other than hiding folders for a cleaner directory.

The “.” is helpful for alphabetical ordering as well. “venv” gets mixed in with other folders while “.venv” is at the top. It also makes it more explicit that it is not meant to be part of the codebase but rather a supporting config type folder… similar to the .vscode, .git folders, etc.

Someone else correct me if I'm wrong since I don't have Windows, but it sounds like this is more a setting that has to do with the security settings on your computer?

@@Indently you're probably right too because it the same command I found on other places. I guess there are settings to be done to tackle the issue.

But the better solution is to use WSL with VSCode - solves many compatibility issues

Maybe it has something to do with execution policies. Run powershell as admin and try the command Set-ExecutionPolicy -ExecutionPolicy Unrestricted and try again the activate command.

@@alfredolagaray This helped so much, thank you!

It helps you separate your code when working with same modules but of different versions, that's just one advantage

Actually, it's a great question. The number of cases where the regular install is sufficient far outweighs the cases where venv is useful (plus it is clunky to use even with a great explanatory video like this). ...so I rarely use venv. I would be interested to hear good use cases other than encapsulation of packages (which can be achieved with a simple requirements.txt file).

​@vincentlaizer I agree with this, but still prefer to avoid...

just type deactivate on windows

I actually didn't describe why they are helpful at all, but I covered how to create and activate them. I will consider the rest for another tutorial :)

I will upload plenty of them, but it's not the only thing I will upload on this channel ;)

Impressive!

We do this at work. Our conclusion was that inside docker a virtual environment makes no sense, because you are already in an isolated environment.

@@squishy-tomato 👍Certainly, Poetry offers distinct advantages over pip. However, for beginners and a general understanding of virtual environments and package installation for their projects, using pip is entirely sufficient.