My Clean Python Setup on Debian Using pyenv (2026 Guide)

Title: My Clean Python Setup on Debian Using pyenv (2026 Guide)

After fighting with repeated “pyenv: command not found” errors every time I opened the terminal, I finally reinstalled and configured pyenv the right way. Here’s the clean and simple setup I now use every day.

What I Ended Up With

  • pyenv 2.6.26
  • Python 3.13.2
  • Isolated virtual environment for each project with automatic activation
  • No more annoying error messages on terminal startup

Daily Workflow (Super Simple)

  1. Open the terminal
  2. Go into your project folder:Bashcd ~/webapp→ The virtual environment activates automatically (you’ll see (webapp) in your prompt)
  3. Verify everything is working:Bashpython --version # Should show: Python 3.13.2 pip --version # Should show: pip 26.0.1
  4. Install packages as needed:Bashpip install requests numpy pandas rich flask
  5. When you’re done, simply leave the project folder:Bashcd ~→ The virtual environment deactivates automatically.

Useful Aliases I Added to ~/.bashrc

Bash

pyenvls     # List all installed Python versions
act         # Manually activate a virtualenv
deact       # Manually deactivate
venv        # Create a new virtualenv

How to Create a New Project (Quick Setup)

Bash

mkdir ~/mynewproject
cd ~/mynewproject
pyenv virtualenv 3.13.2 .
pyenv local .

After this, every time you cd ~/mynewproject, the environment will activate automatically.

This setup has made my Python development life so much smoother. No more fighting with global package conflicts, no more broken environments, and no more annoying errors when opening the terminal. Whether you’re a beginner or an experienced developer, I highly recommend using pyenv with per-project virtual environments on Debian (or any Linux distro).

If you found this guide helpful, feel free to share it or drop a comment with your own Python setup tips!