Python Virtual Environments: Why and How to Use Them

If you’ve ever installed a package for one Python project and broken another, you already understand why Python virtual environments exist. A virtual environment gives each project its own isolated space for packages, so they never interfere with each other. It’s one of the first habits every Python developer should build.

Why Virtual Environments Matter

Imagine you have two projects: Project A needs requests==2.20 and Project B needs requests==2.31. Without a virtual environment, you can only have one version installed globally — and one project will break.

A Python virtual environment solves this by creating a self-contained directory with its own Python interpreter and packages. Each project gets exactly what it needs, nothing more.

Creating and Activating a Virtual Environment

Python 3 ships with venv built in. No installation needed.

# Create a virtual environment called "venv"
python -m venv venv

# Activate it (Linux/Mac)
source venv/bin/activate

# Activate it (Windows)
venv\Scripts\activate

Once activated, your terminal prompt shows the environment name — (venv) — and any pip install commands install only into that environment.

# Install packages inside the virtual environment
pip install flask requests

# Save your dependencies
pip freeze > requirements.txt

The requirements.txt file lists every installed package and version. Anyone who clones your project can recreate your environment exactly:

pip install -r requirements.txt

Deactivating and Managing Environments

# Leave the virtual environment
deactivate

# Delete it (just delete the folder)
rm -rf venv

The venv/ folder should always be added to your .gitignore — it’s large, platform-specific, and easily recreated. Only commit requirements.txt.

Tools That Make This Easier

Once you’re comfortable with venv, look into:

• pipenv — combines pip and virtual environments
• poetry — full dependency management with lock files
• pyenv — manage multiple Python versions

For most beginners, plain venv is perfect. Master it first.

Conclusion

Using a Python virtual environment on every project is a simple habit that prevents hours of debugging dependency conflicts. Create one, activate it, install your packages, and freeze your requirements. Your future self will thank you.

Read next: Writing Clean Python: PEP 8 and Why It Matters

External resource: Python Docs — Virtual Environments