Creating Virtual Environments in Python: A Comprehensive Deep Dive

Virtual environments in Python are isolated spaces that allow you to manage dependencies, packages, and Python versions for individual projects, preventing conflicts and ensuring reproducibility. Python provides built-in tools like venv and third-party options like virtualenv to create these environments. In this blog, we’ll explore how to create and use virtual environments in Python, covering the essentials of venv, practical examples, advanced techniques, and best practices to streamline your development workflow.

What Are Virtual Environments?

link to this section

A virtual environment is a self-contained directory that includes a Python interpreter and a separate set of installed packages, isolated from the system-wide Python installation. Each project can have its own dependencies without interfering with others.

Key Concepts

  • Isolation : Dependencies are scoped to the virtual environment.
  • Interpreter : A copy or link to a specific Python version.
  • Reproducibility : Shareable setup via requirements.txt.

Why Use Virtual Environments?

  • Avoid package version conflicts (e.g., Project A needs requests==2.25.1, Project B needs requests==2.28.0).
  • Test code with different Python versions.
  • Keep the global environment clean.

Example 

# Create a virtual environment
python -m venv myenv

# Activate it (Windows)
# myenv\Scripts\activate

# Activate it (Linux/macOS)
# source myenv/bin/activate

# Install a package
pip install requests

# Deactivate
# deactivate

Getting Started with Virtual Environments in Python

link to this section

The venv Module

Python’s venv module, included in the standard library since Python 3.3, is the recommended tool for creating virtual environments.

Basic Setup 

import venv # Rarely used directly; typically invoked via command line

Creating a Virtual Environment

Use the venv module to set up an environment.

Basic Creation 

# Run in terminal 
python -m venv myenv
  • Creates a directory myenv with:
    • bin/ (or Scripts/ on Windows): Executables like python and pip.
    • lib/: Site-packages for installed libraries.
    • pyvenv.cfg: Configuration file.

Specifying a Python Version 

# Run in terminal 
python3.9 -m venv myenv # Use Python 3.9

Core Operations: Creating and Managing Virtual Environments

link to this section

1. Creating a Virtual Environment

The process is straightforward and consistent across platforms.

Step-by-Step Creation 

# Run in terminal
python -m venv myproject_env

# Directory structure (conceptual, not executable Python code)
# myproject_env/
# ├── bin/ (or Scripts/)
# │   ├── activate
# │   ├── python
# │   ├── pip
# ├── lib/
# │   └── pythonX.X/site-packages/
# └── pyvenv.cfg

Options

  • --upgrade: Upgrade the environment to the latest Python version.
  • --without-pip: Skip installing pip (rarely used). 
# Run in terminal 
python -m venv myenv --upgrade

2. Activating the Virtual Environment

Activation modifies your shell to use the environment’s Python and pip.

On Windows 

# Run in terminal 
myenv\Scripts\activate 
# Prompt changes to: (myenv) >

On Linux/macOS 

# Run in terminal 
source myenv/bin/activate 
# Prompt changes to: (myenv) $

Verification 

# Run in terminal after activation 
python --version 

# Check pip location 
pip --version 
# Output: e.g., pip 23.0 from /path/to/myenv/lib/python3.11/site-packages/pip

3. Installing Packages

Once activated, use pip to install project-specific packages.

Example 

# Run in terminal after activation 
pip install requests 
pip install numpy==1.24.0

Listing Installed Packages 

# Run in terminal
pip list
# Output:
# Package    Version
# ---------- -------
# requests   2.28.2
# numpy      1.24.0
# pip        23.0

4. Deactivating the Virtual Environment

Exit the environment to return to the global Python. 

# Run in terminal 
deactivate

Writing and Managing Virtual Environments: A Major Focus

link to this section

Writing Virtual Environment Setup

Creating and configuring virtual environments involves setting them up for specific projects, installing dependencies, and documenting the setup.

Basic Project Setup 

# Run in terminal
python -m venv venv  # Common name: 'venv'

# Activate
# source venv/bin/activate  # Linux/macOS
# venv\Scripts\activate     # Windows

# Install dependencies
pip install requests flask

Freezing Requirements

Save the current package state: 

# Run in terminal after activation
pip freeze > requirements.txt
# requirements.txt:
# requests==2.28.2
# flask==2.3.2

Reproducing the Environment

Share and recreate the setup: 

# Run in terminal
python -m venv new_env
# source new_env/bin/activate  # Linux/macOS
# new_env\Scripts\activate     # Windows
pip install -r requirements.txt

Customizing the Environment

Modify pyvenv.cfg for specific settings: 

# Edit myenv/pyvenv.cfg manually (not executable Python)
# include-system-site-packages = true  # Access global packages

Using a Specific Python Interpreter 

# Run in terminal
# Assuming Python 3.10 is installed
python3.10 -m venv myenv_310
# source myenv_310/bin/activate
python --version  # Output: Python 3.10.x

Automating Creation with a Script 

import os
import subprocess

def create_venv(name="venv", python_version="python3"):
    subprocess.run([python_version, "-m", "venv", name])
    print(f"Created virtual environment: {name}")

def activate_venv(name="venv"):
    activate_script = os.path.join(name, "bin" if os.name != "nt" else "Scripts", "activate")
    print(f"Run: source {activate_script}" if os.name != "nt" else f"{activate_script}")

create_venv("myenv")
activate_venv("myenv")

Managing Virtual Environments

Managing involves activating, using, and maintaining environments effectively.

Switching Between Environments 

# Environment 1
# source project1_env/bin/activate  # Linux/macOS
# project1_env\Scripts\activate     # Windows
pip install django
# deactivate

# Environment 2
# source project2_env/bin/activate
# project2_env\Scripts\activate
pip install flask
# deactivate

Upgrading Packages 

# Run in terminal
# source venv/bin/activate
pip install --upgrade requests
pip freeze > requirements.txt  # Update requirements

Deleting an Environment 

# Run in terminal (shell commands, not Python)
# rm -rf venv  # Linux/macOS
# rd /s /q venv  # Windows

Checking Environment Isolation 

# Run in terminal after activation
python -c "import sys; print(sys.executable)"
# Output: /path/to/venv/bin/python
pip list  # Shows only venv packages

Handling Multiple Projects 

# Project A
python -m venv project_a_env
# source project_a_env/bin/activate
pip install pandas
# deactivate

# Project B
python -m venv project_b_env
# source project_b_env/bin/activate
pip install numpy
# deactivate

Advanced Techniques

link to this section

1. Using virtualenv

A third-party alternative with more features: 

# Run in terminal
pip install virtualenv
virtualenv myenv  # Similar to venv
virtualenv -p python3.9 myenv  # Specify interpreter

Differences from venv

  • Supports Python 2 (legacy).
  • More configuration options (e.g., --no-site-packages).

2. Virtual Environment with IDEs

  • VS Code : Select interpreter via Python: Select Interpreter (points to venv/bin/python).
  • PyCharm : Automatically detects or creates virtual environments.

Example in VS Code 

# Run in terminal
python -m venv .venv
# Open VS Code, select .venv/bin/python as interpreter

3. Managing with pipenv

A higher-level tool combining virtual environments and dependency management: 

# Run in terminal
pip install pipenv
pipenv --python 3.11  # Creates environment with Python 3.11
pipenv install requests  # Installs and updates Pipfile

Pipfile Example 

# Pipfile (not executable Python, but shown for context)
[[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"

[packages]
requests = "*"

Practical Examples

link to this section

Example 1: Project Setup 

# Run in terminal
python -m venv myapp_env
# source myapp_env/bin/activate  # Linux/macOS
# myapp_env\Scripts\activate     # Windows

# Install dependencies
pip install flask requests

# Save requirements
pip freeze > requirements.txt

# Use in code
python -c "import flask; import requests; print('Setup complete')"
# deactivate

Example 2: Reproducing an Environment 

# Run in terminal
python -m venv clone_env
# source clone_env/bin/activate
pip install -r requirements.txt
pip list  # Verifies installed packages

Example 3: Testing Different Versions 

# Python 3.9 environment
python3.9 -m venv env_39
# source env_39/bin/activate
pip install numpy
python -c "import numpy; print(numpy.__version__)"
# deactivate

# Python 3.11 environment
python3.11 -m venv env_311
# source env_311/bin/activate
pip install numpy

Performance Implications

link to this section

Overhead

  • Creation : Minimal (seconds to copy Python binaries).
  • Runtime : No significant impact; uses same interpreter.

Benchmarking 

# Run in terminal
time python -m venv test_env  # e.g., real 0m0.5s

Virtual Environments vs. Other Tools

link to this section
  • Conda : Manages environments and non-Python dependencies.
  • Docker : Full system isolation, not just Python.
  • Global Installs : Risk of conflicts without virtual environments.

Conda Example 

# Run in terminal
conda create -n myenv python=3.11
conda activate myenv

Best Practices

link to this section
  1. Use Per Project : Create a virtual environment for each project.
  2. Standard Naming : Use venv or .venv for consistency.
  3. Document Dependencies : Always maintain a requirements.txt.
  4. Activate in Scripts : Include activation in automation (e.g., .bashrc, CI/CD).
  5. Clean Up : Delete unused environments to save space.

Edge Cases and Gotchas

link to this section

1. Path Issues 

# Wrong Python version 
python -m venv myenv # Uses default python; specify if needed

2. Activation Failure 

# Missing activation script 
# source myenv/bin/activate # Ensure correct path

3. Global Packages 

# Unexpected global access 
# Check pyvenv.cfg: include-system-site-packages = false

Conclusion

link to this section

Creating virtual environments in Python, primarily with the venv module, is a fundamental skill for managing project dependencies and ensuring a clean, reproducible development setup. Writing virtual environment setups involves creating, activating, and installing packages, while managing them includes switching, upgrading, and documenting configurations. From isolating project dependencies to testing across Python versions, virtual environments enhance flexibility and reliability. Mastering their creation, usage, and integration with tools like pipenv or IDEs equips you to maintain organized, conflict-free Python workflows with ease.