Why Use Python Virtual Environments?

If you’ve ever run into the dreaded “it works on my machine” issue, you know how frustrating it can be. Different projects might require different package versions, leading to conflicts. Enter Python virtual environments! They allow you to isolate your projects, ensuring that dependencies don’t interfere with each other. The result? A smooth development experience where your projects are reproducible and free from drama.

1. Create a Virtual Environment

Creating a virtual environment is a breeze. Open your terminal or command prompt and run the following command:

# Recommended - creates folder named .venv (very common convention in 2025)
python -m venv .venv

You can also create it with alternative names:
– python -m venv venv
– python -m venv myproject-env
– python3 -m venv .venv (for some Linux/macOS users)
– py -m venv .venv (if you’re using Windows with Python Launcher)

Pro Tip: Using .venv is the best practice in 2025. It’s a hidden folder in many file explorers, so it keeps your workspace tidy. Plus, many editors like VS Code and PyCharm auto-detect and activate it.

2. Activate the Virtual Environment

After creating your environment, you need to activate it. The command varies by operating system:

Windows (cmd):

.venv\Scripts\activate

Windows (PowerShell):

.venv\Scripts\Activate.ps1

Note: You might need to set the execution policy in PowerShell.

macOS / Linux / WSL:

source .venv/bin/activate

Here’s a neat trick for Linux/macOS users:

python -m venv .venv && source .venv/bin/activate

This combines creation and activation in one line!

Once activated, you should see (.venv) or (venv) at the start of your terminal prompt. To confirm it’s working, run:

python --version  # should match the version used to create the venv
pip list          # should show almost nothing (only pip, setuptools, wheel)

3. Install Packages

With your virtual environment active, it’s time to install packages. You can do this using pip. For example:

pip install requests pandas numpy

If you have a requirements.txt file, installing from it is straightforward:

pip install -r requirements.txt

Quick Reminder: It’s a good habit to upgrade pip itself before installing other packages. Just run:

pip install --upgrade pip

4. Create a requirements.txt File

If you want to save the list of installed packages for future use, you can create a requirements.txt file. This is useful for sharing your project with others or for deployment.

To generate it from your current environment, use the following command:

pip freeze > requirements.txt

This command captures all the packages in your virtual environment and saves them to a text file. Now anyone else can replicate your environment by running pip install -r requirements.txt.

5. Deactivating the Virtual Environment

When you’re done working in your virtual environment, it’s a good idea to deactivate it. Just type:

deactivate

This command will return you to the system’s default Python environment. It’s a simple step but helps keep your workspace organized.

Final Thoughts

Using Python virtual environments is a best practice for developers. It keeps your projects clean, dependencies isolated, and makes your workflow smoother. If you follow these steps, you should be well on your way to managing your Python projects like a pro.

Need more help? Check the latest CrushEdge posts.