PYTHON

python virtual environment

python3 -m venv env
python -m virtualenv env #py2

source env/bin/activate

#all this is on same directory

virtual env in python

pip install --user virtualenv
py -m venv env
.envScriptsactivate

python venv

# Ubuntu/Debian
apt-get install python3-venv
python3 -m venv .venv
source .venv/bin/activate

# python 2
python -m virtualenv env

venv python

python3 -m venv env    # create env
source env/bin/activate    # activate env
deactivate    # deactivate env
rm -r env/    # delete env in Linux
pip freeze    # show all packages installed
pip install -r requirements.txt   # install all packages
pip freeze > requirements.txt    # create automatically requirements.txt

pyton venv

python -m venv newVirtualEnv				//create new virtual env
source newVirtualEnv/bin/activate  			//activate-lunix|unix
./newVirtualEnv/Scripts/activate.ps1 			//activate-Windows powershell
./newVirtualEnv/Scripts/activate.bat 		//activate-Windows cmd
cd newVirtualEnv/Scripts && . activate		//activate-Windows git bash:
  
//--Windows Execution_Policies error--
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

// check if using venv active - CLI does not have (newVirtualEnv) 
pip -V

python venv

#------FOR LINUX/MAC---------#
sudo apt-get install build-essential libssl-dev libffi-dev python-dev #installing requirements
sudo apt-get install -y python3-venv #installing venv 
python3 -m venv env #creating virtual env
source env/bin/activate #activating virtual env


#-------FOR WINDOWS----------# 
py -m pip install --user virtualenv #installing venv
py -m venv env #creating virtual env
.envScriptsactivate #activating virtual env

python virtual env

$ pip install virtualenv

python venv

### install virtualenvwrapper ###
pip install virtualenvwrapper-win
### Add an environment variable WORKON_HOME to specify the path to store environments. By default, this is %USERPROFILE%Envs. ###

### ↓↓↓ use cmd or cmder (don't use ps terminal) for any of the following commands ↓↓↓ ###

### list venvs ###
lsvirtualenv

### create venv (automatically activated after creation) ###
mkvirtualenv <name>

### remove venv ###
rmvirtualenv <name>

### activate venv ###
workon <name>

### deactivate venv ###
deactivate


### General Syntax ###
mkvirtualenv [-a project_path] [-i package] [-r requirements_file] [virtualenv options] <name>

virtual environment python

py -m venv env ## For windows and Python 3
.envScriptsactivate
deactivate

python virtualenv

python -m venv my_env
source my_env/bin/activate

python virtualenv

python -m venv my_env

python virtual environment

python -m venv myenv

myenv/Scripts/activate

python virtualenv venv

python -m venv venv

virtualenv --python

virtualenv venv --python=python3.10

#you can change python version (eg. python3.10) , Folder name (eg. venv)

virtual environment python

python3 -m venv env  ##For linux
source env/bin/activate
deactivate

python virtual env

$ virtualenv --version

virtual env in python

python3 -m venv tutorial-env

python virtual env

$ source venv/bin/activate

python venv

python -m venv flask_env  # Creating an isolated environment
source flask_env/bin/activate # Activate virtual environment
deactivate #deactivate

python virtual env

$ cd project_folder
$ virtualenv venv

python virtual environment

# Virtual Environments ("virtualenvs") keep
# your project dependencies separated.
# They help you avoid version conflicts
# between packages and different versions
# of the Python runtime.

# Before creating & activating a virtualenv:
# `python` and `pip` map to the system
# version of the Python interpreter
# (e.g. Python 2.7)
$ which python
/usr/local/bin/python

# Let's create a fresh virtualenv using
# another version of Python (Python 3):
$ python3 -m venv ./venv

# A virtualenv is just a "Python
# environment in a folder":
$ ls ./venv
bin      include    lib      pyvenv.cfg

# Activating a virtualenv configures the
# current shell session to use the python
# (and pip) commands from the virtualenv
# folder instead of the global environment:
$ source ./venv/bin/activate

# Note how activating a virtualenv modifies
# your shell prompt with a little note
# showing the name of the virtualenv folder:
(venv) $ echo "wee!"

# With an active virtualenv, the `python`
# command maps to the interpreter binary
# *inside the active virtualenv*:
(venv) $ which python
/Users/dan/my-project/venv/bin/python3

# Installing new libraries and frameworks
# with `pip` now installs them *into the
# virtualenv sandbox*, leaving your global
# environment (and any other virtualenvs)
# completely unmodified:
(venv) $ pip install requests

# To get back to the global Python
# environment, run the following command:
(venv) $ deactivate

# (See how the prompt changed back
# to "normal" again?)
$ echo "yay!"

# Deactivating the virtualenv flipped the
# `python` and `pip` commands back to
# the global environment:
$ which python
/usr/local/bin/python

python virtual env

$ virtualenv -p /usr/bin/python2.7 venv

python venv

python3 -m venv tutorial-env
// start it 
source tutorial-env/bin/activate
// end it 
deactivate

python venv

source <folder-env>/bin/activate

python virtual environment

How to make a virtual environment in Python! (Windows)

py -m venv [virtual environment name]
[virtual environment name]Scriptsactivate #use "" not "/"

DO YOUR CODE IN HERE, SAVES TIME WITH PACKAGE MANAGEMENT!

virtual environment python

#create new virtual environment
python3 -m venv /path/to/new/virtual/environment

what is python virtual environment

# At its core, the main purpose of Python virtual environments is to 
# create an isolated environment for Python projects. This means that 
# each project can have its own dependencies, regardless of what 
# dependencies every other project has.

python virtual env

$ export VIRTUALENVWRAPPER_PYTHON=/usr/bin/python2.7

python virtual env

$ pip install --user pipenv