Virtual Environment
Contributors: Alanna Zhou, Shungo Najima
Last updated
Was this helpful?
Contributors: Alanna Zhou, Shungo Najima
Last updated
Was this helpful?
You can consult some for more information!
virtualenv
Navigate to the directory that you want to be coding in, and make sure you have virtualenv
installed
venv
folderYou could actually name this anything you want, but it's good practice to call it venv
You create this folder so you can activate later to essentially "enter your virtual environment"
venv
folder You can see if it's been created with ls
for MacOS or dir
for Windows
MacOS command to activate virtual environment:
Windows command to activate virtual environment:
If you are getting an error that reads: "cannot be loaded because the execution of scripts is disabled on this system".
, close PowerShell (if open), look up PowerShell on Windows search, click on "run as administrator", then run the command below:
If you're still getting an error, try running these commands on PowerShell instead of Command Prompt.
requirements.txt
Now that you're in the environment, your terminal should have a (venv)
next to your cursor, so you can now install the requirements to setup your virtual environment
Make sure requirements.txt
exists where you are running this command! (again, you can check this using ls
/dir
to list everything in your current directory).
If you are curious, -r
is a flag that installs the requirements recursively to install all requirements defined in requirements.txt
.3
Now you can run code with the dependencies that were installed by Step 4.
Here's just an example:
If you're done developing for your project for the time being, or if you want to work on another project that has another virtual environment, you can deactivate the one that you're currently in
Steps #1, 2, and 4 are only done once for every new project you'll be creating a virtual environment for.
Steps #3, 5, and 6 are what you'll be using every time after that to use your virtual environment!
requirements.txt
There are two issues that cause this problem:
You are not in the directory where requirements.txt
exists. You'll know this is the case if enter ls
(MacOS) or dir
(Windows) into your terminal and you don't see requirements.txt
or if you didn't spell it right in your command.
If you are curious as to what exactly this is doing to your computer, it is allowing the current user to run scripts. RemoteSigned
is one of many execution policies which you can read about , and CurrentUser
is one of many scopes which you can read about .
You are trying to do pip3 install -r requirements.txt
inside of a correctly created and activated venv
, but your venv
is nested within a path that contains a folder that has a space in the name. Here's a good that explains the issue.