Making Sense of Python Virtual Environment Tools and Workflows
summary
Compares specific tools and behaviours: venv links vs virtualenv copies (venv is stdlib since Python 3.3), virtualenvwrapper stores envs centrally, pyenv/pyenv-virtualenv manage Python versions, and pip installs into site‑packages so use virtualenvs to isolate projects. Pipenv is project-scoped, uses Pipfile/Pipfile.lock with hashes and can be slow but works on Heroku; Conda/Anaconda bundles interpreters for multi‑language/data‑science use; Poetry and Hatch add packaging plus stricter dependency resolution. Recommends venv for general use, Pipenv for web projects, Conda for multi‑language stacks.
AI-written summary · about
chapters (13)
- 0:00Intro
- 8:10Virtual Environment
- 12:35Virtualenv Wrapper
- 15:13VNF
- 18:32Pippin
- 22:19Piin
- 22:37PiVN
- 22:59Condor
- 23:46Which tool to use
- 25:25Summary
- 25:46Conclusion
- 26:40Questions
- 33:03Perp
related talks
30mPython Versions and Dependencies Made Easy
33mVirtual Environments and Dependency Management in Python
36mPipenv: The Future of Python Dependency Management
29mDon't Cross The Streams - An Introduction to Virtual Environments
28mPyenv + Poetry: how to manage your Python environments simply
28mBreaking Free from Virtual Environments Python's New Paradigm for 2026
33mThe past, present, and future of virtual environments
30mBootstrapping Your Local Python Environment