This tutorial will walk through the basics of Python 3 virtual environments. The official documentation is available at https://docs.python.org/3/library/venv.html. All of these commands are run from your command prompt/shell/terminal, not from within Python.
What is a Python virtual environment
A virtual environment is a directory that contains its own installation of Python and its own set of libraries (site packages).
Why use it
Python virtual environments are particularly useful if you have multiple versions of Python installed, or you work on many projects that have different library requirements.
By default, without a virtual environment, all
will use the default executables, usually your system install. It is better
to keep your system Python clean of unnecessary site packages. Otherwise,
over time, you will add lots of things to your system packages and things
might conflict and cause problems. Using an isolated environment for each
project ensures easy reproducability and reduced conflict.
Create a venv
To create a virtual environment, run in your command prompt or shell:
# Create a virtual environment named `my_venv` in your current directory python3 -m venv my_venv # Optionally inherit the system site package python3 -m venv my_venv --system-site-packages
It can be useful at times to inherit the system site packages with
system-site-packages flag. This is
particularly helpful if you have a library that is difficult to build or install,
or is provided by another package provider (like a Linux
In these cases, inheriting the site packages may be necessary to avoid
rebuilding libraries. In general, this is rare and I would avoid doing it
unless you have a specific need to do so.
How to use a virtual environment
To use a virtual environment, you activate and deactivate them. This
will modify your
PATH environment variable.
Activate a virtual environment
Once activate, you use
pip like normal, except they will
point to your virtual environment. When you activate a virtual environment,
a few other things happen:
PATHswitches to the virtual environment Python
- Python will have access to the site packages from the virtual environment only
pippackages and things installed with
setup.pywill go in your virtual environment's site packages
PATHwill be updated to include the Python virtual environment's script directory. Any executables installed through a package will be available in your shell path.
Deactivate a virtual environment
To "exit" a virtual environment,
See which python and pip are being used
You can always check which
PATH environment variable
is pointing to by using the following commands.
which pip which python
where pip where python
Find site packages directory
To see what directories are being used to search for packages, invoke
site module directly by running:
python -m site
View installed packages
To list the installed packages when a virtual environment is active, from the shell run:
Install packages to virtual environment
Once the virtual environment is activated (which you can confirm with
where python), you can install packages by using
pip or running a
that uses distutils. The installed
packages will go in to your virtual environment's site packages directory.
# Install using `pip` and pypi.org packages python -m pip install flask pip install flask # Equivalent when virtual environment is activated # Install from source python setup.py install
You can also use a
requirements.txt file to install a group of modules.
This is useful for quickly setting up a new virtual environment.
# requirements.txt contains list of packages to install # and can be created with `pip freeze > requirements.txt` pip install -r requirements.txt
- If Python is not finding a package that you are sure you installed, it is
probably installed to a different instance/virtual environment.
Make sure your IDE is using the right virtual environment and you
installed the packages to the right environment. Use
python -m pip listto check.
pythonmay refer to different version of python depending on whether you are using it in your command prompt/shell, pycharm, visual studio code, or another editor. Don't always assume
pythonfrom different places is calling the same Python environment.
- Avoid using
pipby itself. Using
python -m pipwill always guarantee you are using the
pipassociated with that specific
pythonbeing called, instead of potentially calling a
pipassociated with a different
- Sometimes there is a
pip3to go with
python3to differentiate python 2 executables
- You can call a python directly from path without having to activate venv /path/to/venv/python and it will use the site packages from the virtual environment this is particularly useful for cron jobs where you want to invoke python directly without the extra activating a virtual environment
- Sometimes Linux distributions require you to install virtualenv as a separate package. For example
sudo apt install python3-virtualenv.
- I recommend using a separate virtual environment for each project.
- You should never copy or move around virtual environments. Always create new ones.
- Ignore the virtual environment directories from repositories. For example,
After reading this you should have an idea of how to set up and use a basic virtual environment with Python 3.