PIP Package Manager

Intermediate ~25 min read

PIP (Pip Installs Packages) is Python's package manager - your gateway to over 400,000 packages on PyPI (Python Package Index). From web frameworks like Flask and Django to data science libraries like NumPy and Pandas, pip lets you easily install, upgrade, and manage third-party packages. Understanding pip and virtual environments is essential for any Python developer working on real-world projects!

Essential PIP Commands

PIP commands run in your terminal (Command Prompt, PowerShell, or Terminal), not in Python. The most common commands are pip install to add packages, pip uninstall to remove them, and pip list to see what's installed. You can also specify exact versions for reproducible builds.

# PIP Command Reference
# Note: These are terminal commands, shown here for reference

print("=== Essential PIP Commands ===")
print("""
# Install a package
pip install package_name

# Install specific version
pip install package_name==1.2.3

# Install minimum version
pip install 'package_name>=1.2.0'

# Upgrade a package
pip install --upgrade package_name

# Uninstall a package
pip uninstall package_name

# List installed packages
pip list

# Show package info
pip show package_name

# Search PyPI (deprecated, use web)
# pip search package_name

# Check for outdated packages
pip list --outdated
""")

print("=== Installing Multiple Packages ===")
print("""
# From requirements.txt
pip install -r requirements.txt

# Install several at once
pip install requests flask numpy

# Install with dependencies
pip install package_name[extra_deps]
""")

print("=== Useful Flags ===")
print("""
--user       Install for current user only
--no-cache   Skip cache when downloading
-q, --quiet  Minimal output
-v, --verbose Detailed output
""")

Output

Click Run to execute your code

pip vs pip3: On systems with both Python 2 and 3, use pip3 for Python 3 packages. On newer systems with only Python 3, pip and pip3 are usually the same. To be safe, use python -m pip install package which always uses the pip for the current Python interpreter.

Managing Dependencies with requirements.txt

The requirements.txt file lists all packages your project needs. It's the standard way to share dependencies - anyone can recreate your environment by running pip install -r requirements.txt. Use pip freeze to generate this file from your current environment.

# Working with requirements.txt

print("=== requirements.txt Format ===")
print("""
# Example requirements.txt file:
# ---------------------------------
requests==2.28.0
flask>=2.0.0
numpy
pandas>=1.3.0,<2.0.0
python-dateutil~=2.8.0
---------------------------------

Version specifiers:
  ==1.2.3    Exact version
  >=1.2.0    Minimum version
  <=1.2.0    Maximum version
  ~=1.2.0    Compatible release (~=1.2.0 means >=1.2.0, <1.3.0)
  !=1.2.3    Exclude version
  >=1.2,<2.0 Range
""")

print("=== Creating requirements.txt ===")
print("""
# Freeze current environment
pip freeze > requirements.txt

# This creates a file with all installed packages
# and their exact versions
""")

print("=== Installing from requirements.txt ===")
print("""
# Install all packages listed
pip install -r requirements.txt

# Common workflow:
# 1. Clone project
# 2. Create virtual environment
# 3. pip install -r requirements.txt
# 4. Start coding!
""")

# Simulating checking installed packages
print("\n=== Check If Package Is Installed ===")
packages = ["requests", "flask", "numpy", "nonexistent_package"]

for pkg in packages:
    try:
        __import__(pkg)
        print(f"{pkg}: Installed")
    except ImportError:
        print(f"{pkg}: Not installed")

Output

Click Run to execute your code

Version Specifiers:
==1.2.3 - Exact version (most reproducible)
>=1.2.0 - Minimum version (allows updates)
~=1.2.0 - Compatible release (>=1.2.0, <1.3.0)
>=1.2,<2.0 - Version range (flexible but bounded)

Virtual Environments

Virtual environments solve a critical problem: different projects needing different package versions. Each virtual environment is an isolated Python installation with its own packages. This is a must-know skill for professional Python development - always use virtual environments for your projects!

# Virtual Environments
# Isolate project dependencies

print("=== Why Virtual Environments? ===")
print("""
Problem: Different projects need different versions
- Project A needs requests==2.25.0
- Project B needs requests==2.28.0
- Installing one breaks the other!

Solution: Virtual environments
- Each project gets its own Python environment
- Packages installed in isolation
- No conflicts between projects
""")

print("=== Creating Virtual Environments ===")
print("""
# Using venv (built-in, Python 3.3+)
python -m venv myenv

# This creates a folder 'myenv' with:
# - Python interpreter
# - pip
# - Empty site-packages
""")

print("=== Activating Virtual Environment ===")
print("""
# Windows
myenv\\Scripts\\activate

# macOS/Linux
source myenv/bin/activate

# Your prompt changes to show active env:
# (myenv) $

# Now pip install only affects this env!
""")

print("=== Deactivating ===")
print("""
# Simply run:
deactivate

# Prompt returns to normal
""")

print("=== Best Practices ===")
print("""
1. One virtual env per project
2. Add 'venv/' to .gitignore
3. Use requirements.txt for dependencies
4. Document Python version needed

# Typical workflow:
python -m venv venv
source venv/bin/activate  # or venv\\Scripts\\activate
pip install -r requirements.txt
# ... work on project ...
deactivate
""")

Output

Click Run to execute your code

Don't Commit Your venv! Add venv/ or .venv/ to your .gitignore file. Virtual environments are large, machine-specific, and can be recreated from requirements.txt. Only commit the requirements.txt file, not the entire virtual environment folder.

Using Installed Packages

Once installed, packages are imported just like standard library modules. Python's ecosystem includes packages for nearly everything: web development, data science, machine learning, API clients, automation, and more. Learning to find and use the right packages is a superpower!

# Using Installed Packages

# 1. Check Python and pip version
import sys
print("=== Environment Info ===")
print(f"Python version: {sys.version}")
print(f"Python path: {sys.executable}")
print()

# 2. List available modules
print("=== Some Standard Library Modules ===")
stdlib_modules = [
    "json", "datetime", "math", "random",
    "os", "sys", "re", "collections"
]
for mod in stdlib_modules:
    try:
        __import__(mod)
        print(f"  {mod}: Available")
    except ImportError:
        print(f"  {mod}: Not available")
print()

# 3. Popular third-party packages
print("=== Popular Third-Party Packages ===")
print("""
Data Science:
  numpy       - Numerical computing
  pandas      - Data analysis
  matplotlib  - Plotting

Web Development:
  requests    - HTTP requests
  flask       - Web framework
  django      - Full-featured framework

Utilities:
  python-dateutil - Date utilities
  pillow      - Image processing
  pyyaml      - YAML parsing
""")

# 4. Using a package (example with json, always available)
print("=== Example: Using a Package ===")
import json

data = {"name": "Alice", "score": 95}
json_str = json.dumps(data, indent=2)
print(f"JSON output:\n{json_str}")

Output

Click Run to execute your code

Common Mistakes

1. Installing globally without virtual environment

# Wrong - installs globally, can cause conflicts
pip install flask

# Better - always use virtual environment
python -m venv venv
source venv/bin/activate  # or venv\Scripts\activate on Windows
pip install flask

# Now flask is isolated to this project

2. Not pinning versions in production

# requirements.txt - Bad for production
requests
flask
numpy

# requirements.txt - Good for production
requests==2.28.0
flask==2.2.2
numpy==1.24.0

# Generate pinned requirements:
pip freeze > requirements.txt

3. Forgetting to activate virtual environment

# Wrong - installs to wrong Python!
python -m venv venv
pip install requests  # Still using global pip!

# Correct - activate first!
python -m venv venv
source venv/bin/activate  # IMPORTANT!
pip install requests  # Now goes to venv

# Check which pip you're using:
which pip  # Should show path inside venv

4. Committing virtual environment to git

# .gitignore - Add these lines!
venv/
.venv/
env/
.env/
__pycache__/
*.pyc

# Only commit requirements.txt
# Others can recreate the environment with:
pip install -r requirements.txt

5. Using pip install in Python code

# Wrong - don't install packages from Python
import pip
pip.main(['install', 'requests'])  # Bad practice!

# Correct - install from terminal
# $ pip install requests

# If you must install programmatically:
import subprocess
import sys
subprocess.check_call([sys.executable, "-m", "pip", "install", "requests"])

Exercise: Project Setup

Task: Write the commands for a proper project setup workflow.

Requirements:

Create a virtual environment named 'venv'
Activate the virtual environment
Install requests and flask packages
Save dependencies to requirements.txt

Output

Click Run to execute your code

Show Solution

# Project setup commands (run in terminal, not Python)
print("=== Project Setup Commands ===")
print()
print("# 1. Create virtual environment")
print("python -m venv venv")
print()
print("# 2. Activate virtual environment")
print("# Windows:")
print("venv\\Scripts\\activate")
print("# macOS/Linux:")
print("source venv/bin/activate")
print()
print("# 3. Install packages")
print("pip install requests flask")
print()
print("# 4. Save dependencies")
print("pip freeze > requirements.txt")
print()
print("# Bonus: Verify installation")
print("pip list")
print("python -c \"import requests, flask; print('Success!')\"")
print()
print("# When done working:")
print("deactivate")

Summary

Install: pip install package_name
Specific version: pip install package==1.2.3
Upgrade: pip install --upgrade package
Uninstall: pip uninstall package
List packages: pip list or pip freeze
requirements.txt: pip install -r requirements.txt
Create venv: python -m venv venv
Activate: source venv/bin/activate (Linux/Mac) or venv\Scripts\activate (Windows)
Deactivate: deactivate
Best practice: Always use virtual environments for projects

What's Next?

Congratulations on completing the Modules & Packages module! You now know how to work with Python's standard library modules and install third-party packages. Next, we'll learn about File Handling - reading from and writing to files, which is essential for data processing, configuration, and persistence!

Previous RegEx

Next Reading Files

Essential PIP Commands

Managing Dependencies with requirements.txt

Virtual Environments

Using Installed Packages

Common Mistakes

1. Installing globally without virtual environment

2. Not pinning versions in production

3. Forgetting to activate virtual environment

4. Committing virtual environment to git

5. Using pip install in Python code

Exercise: Project Setup

Summary

What's Next?

Enjoying these tutorials?