Python Environment Management Workflow

🎯 Overview

A hybrid Python development setup that allows seamless switching between modern Python 3.12.3 for personal projects and legacy Python 3.8.13 for school/work projects.

⚙️ Core Configuration

🤩 Zsh Configuration (~/.zshrc)

# =========================
# 🐍 PYENV CONFIGURATION
# =========================
export PYENV_ROOT="$HOME/.pyenv"
export PATH="$PYENV_ROOT/bin:$PATH"
eval "$(pyenv init --path)"
eval "$(pyenv init -)"

# =========================
# 📦 PIPENV CONFIGURATION
# =========================
export PIPENV_VENV_IN_PROJECT=1

🧠 Installed Python Versions

• System Python: 3.12.3 (Ubuntu default)

• Pyenv Python 3.12.3: For modern projects (optional but recommended)

• Pyenv Python 3.8.13: For legacy/school projects

🚀 Workflow

🧪 For Modern Projects (Python 3.12.3)

# Create project
mkdir my_modern_project
cd my_modern_project

# Install dependencies (auto-uses Python 3.12.3)
pipenv install flask requests pandas

# Verify Python version
pipenv run python --version  # Python 3.12.3

# Activate environment
pipenv shell

🏫 For Legacy Projects (Python 3.8.13)

# Create project
mkdir school_project
cd school_project

# Install dependencies with explicit Python version
pipenv --python 3.8 install django flask

# Verify Python version
pipenv run python --version  # Python 3.8.13

# Activate environment
pipenv shell

📁 Project Structure

~/codeWorld2/
├── my_modern_api/          # Python 3.12.3
│   ├─ .venv/
│   ├─ Pipfile
│   └─ Pipfile.lock
├── school_assignment/      # Python 3.8.13  
│   ├─ .venv/
│   ├─ Pipfile
│   └─ Pipfile.lock
└── quick_scripts/          # Python 3.12.3
    ├─ .venv/
    ├─ Pipfile
    └─ Pipfile.lock

🛠️ Key Commands

🧬 Environment Management

# Create new environment
pipenv install package_name

# Activate environment
pipenv shell

# Run commands without activating
pipenv run python script.py

# Deactivate environment
exit

# Remove environment
pipenv --rm

🤩 Python Version Management

# List available Python versions
pyenv versions

# Set global Python version
pyenv global 3.12.3

# Set local Python version for project
pyenv local 3.8.13

# Install new Python version
pyenv install 3.8.13

📦 Dependency Management

# Install production dependency
pipenv install requests

# Install development dependency
pipenv install --dev pytest

# Generate requirements.txt
pipenv lock -r > requirements.txt

# Install from existing Pipfile
pipenv install

🔄 Workflow Examples

🧠 Starting a New Modern Project

mkdir my_fastapi_app
cd my_fastapi_app
pipenv install fastapi uvicorn
pipenv run python --version  # 3.12.3
pipenv shell
# Start coding...

🏫 Working on School Assignment

mkdir phase3_challenge  
cd phase3_challenge
pipenv --python 3.8 install django pandas
pipenv run python --version  # 3.8.13
pipenv shell
# Work on assignment...

🤟 Cloning Existing Repository

git clone <project-url>
cd project-name

# Check Pipfile for required Python version
cat Pipfile

# If Python 3.8 required:
pipenv --python 3.8 install

# If modern Python (3.12.3):
pipenv install

🌟 Benefits

✅ Isolation

• Each project has isolated dependencies

• No system-wide package conflicts

• Virtual environments stored in project folders

✅ Version Control

• Modern projects use latest Python features

• Legacy projects maintain compatibility

• Easy to switch between versions

✅ Reproducibility

• Pipfile.lock ensures consistent dependencies

• Clear Python version requirements

• Easy to share and collaborate

⚠️ Troubleshooting

🤩 Common Issues

Wrong Python version in environment
→ Use pipenv --python X.X install explicitly

Package installation failures
→ Check package compatibility with your Python version

Environment not activating
→ Ensure PIPENV_VENV_IN_PROJECT=1 is set

🗾 Verification Commands

# Check current Python
python --version

# Check pipenv Python
pipenv --py

# Check pyenv status
pyenv version

# List environments
pipenv --venv

📝 Best Practices

• Always use explicit Python versions for legacy projects

• Commit both Pipfile and Pipfile.lock

• Use descriptive project names to separate modern vs legacy

• Regularly update dependencies in modern projects

• Test legacy projects after environment changes

🔗 Related Tools

• pyenv → Python version management

• pipenv → Virtual environment & dependency management

• pip → Package installer (used internally by pipenv)

Last updated: {{date:YYYY-MM-DD}}