Python Virtual Environments Explained: venv, virtualenv, and Modern Alternatives

The Problem: Dependency Conflicts

Imagine you're working on two Python projects simultaneously. Project A requires requests==2.28 while Project B needs requests==2.31. Without isolation, installing one version breaks the other. This is the core problem that virtual environments solve.

A virtual environment is an isolated Python environment with its own interpreter, packages, and dependencies — completely separate from your system Python and other projects.

The Built-in Solution: venv

Python 3.3+ ships with venv built into the standard library. No installation required:

# Create a virtual environment
python -m venv .venv

# Activate it (Linux/macOS)
source .venv/bin/activate

# Activate it (Windows)
.venv\Scripts\activate

# Deactivate when done
deactivate

Once activated, pip install installs packages only into that environment, and python refers to the environment's interpreter.

Managing Dependencies with requirements.txt

To share your environment's dependencies with teammates or deploy to a server:

# Freeze current packages
pip freeze > requirements.txt

# Recreate environment elsewhere
pip install -r requirements.txt

Modern Alternative: uv

uv is a blazing-fast Python package manager and project tool written in Rust by the team behind Ruff. It handles virtual environments, dependency resolution, and package installation dramatically faster than pip:

pip install uv

# Create and manage a project
uv init my-project
cd my-project
uv add requests  # Installs and tracks dependency
uv run python main.py  # Runs in the managed environment

uv is rapidly gaining adoption and is worth considering for new projects in 2024 and beyond.

Poetry: Full Project Management

Poetry combines dependency management, virtual environments, and package publishing into one tool. It uses a pyproject.toml file for project configuration:

pip install poetry

poetry new my-project
cd my-project
poetry add requests
poetry install  # Creates venv and installs all deps
poetry run python main.py

Poetry is particularly popular for library development and projects that will be published to PyPI.

Tool Comparison

Tool	Built-in?	Speed	Lock File	Best For
venv + pip	Yes	Moderate	No (manual)	Simple projects
uv	No	Very Fast	Yes	Modern projects
Poetry	No	Moderate	Yes	Libraries, publishing
Conda	No	Slow	Yes	Data science

Best Practices

• Always use a virtual environment — even for small scripts.
• Name your environment .venv and add it to .gitignore.
• Use a lock file (Poetry's poetry.lock or uv's uv.lock) to pin exact dependency versions for reproducible builds.
• Document setup instructions in your README.md.
• Pin Python version with a .python-version file (used by pyenv and uv).

Conclusion

Virtual environments are non-negotiable for professional Python development. Start with venv if you want zero setup friction, and consider migrating to uv or Poetry as your project complexity grows. The key habit is simply using one — always.