virtualenvwrapper

virtualenvwrapper
Name	virtualenvwrapper
Developer	Doug Hellmann
Programming language	Python
Operating system	Cross-platform
License	MIT License
Website	Official project pages and repositories

virtualenvwrapper is a set of extensions to the Python virtualenv tool that provides higher-level wrappers and utilities to manage multiple isolated Python environments. It streamlines environment creation, activation, deactivation, and project-directory integration for developers working across projects tied to institutions such as Google, Facebook, Netflix, Dropbox, and Spotify. Adopted by engineers at companies including Mozilla, Red Hat, Canonical, Microsoft, and IBM, it complements workflows used in organizations like NASA, European Space Agency, Intel, and ARM Holdings.

Overview

virtualenvwrapper builds on virtualenv and the Python distutils/setuptools ecosystem to simplify environment lifecycle tasks familiar to contributors at Apache Software Foundation, Linux Foundation, Python Software Foundation, and OpenStack Foundation. It integrates with shells and platforms such as Bash, Zsh, Fish, macOS, and Ubuntu to standardize where environments live, drawing patterns similar to tooling from Docker, Vagrant, Ansible, and Chef. Teams at GitHub, GitLab, Bitbucket, and Atlassian often use virtualenvwrapper together with CI systems like Jenkins, Travis CI, CircleCI, and GitHub Actions.

Installation and setup

Installers reference package managers and platforms such as pip, PyPI, Homebrew, and apt (software); platform-specific examples mirror guides from Debian, Fedora, CentOS, Arch Linux, and OpenSUSE. Setup often cites shell startup files used at GNU Project, FreeBSD, NetBSD, and OpenBSD. Administrators from organizations including Oracle Corporation, SAP SE, Bloomberg L.P., and Goldman Sachs adapt configuration steps to enterprise environments managed with tools like Puppet, SaltStack, and Systemd. For virtualenvwrapper to work, users ensure dependencies such as virtualenv and the Python runtime distributions maintained by CPython or vendor forks like PyPy are installed.

Key features and commands

virtualenvwrapper exposes commands and behaviors analogous to capabilities in projects like pipenv, Poetry, Conda, and pyenv. Primary commands mirror common operations in software engineering at firms such as Twitter, LinkedIn, Uber, and Airbnb: create, remove, workon, lsvirtualenv, and mkvirtualenv. Integration points echo patterns from Makefile workflows, GNU Autotools, and task runners used at Netflix and Spotify. Features include centralized environment storage patterned after directory conventions from XDG Base Directory Specification, automatic project directory switching used in Emacs and Vim, and hook scripts comparable to git hooks utilized at GitLab and GitHub Enterprise.

Usage patterns and workflows

Developers apply virtualenvwrapper in project workflows alongside version control systems like Git, Subversion, and Mercurial and CI/CD stacks used at Google Cloud Platform, Amazon Web Services, Microsoft Azure, and Heroku. Common workflows mirror those in open-source projects managed by Apache Software Foundation or released through PyPI and incorporate dependency management strategies promoted by NumFOCUS projects such as pandas, NumPy, and SciPy. Teams in research labs at MIT, Stanford University, Harvard University, California Institute of Technology, and ETH Zurich use it to reproduce experiments similar to reproducibility efforts from Allen Institute for AI and Broad Institute.

Configuration and customization

virtualenvwrapper supports environment variables and hook scripts that integrate with editor ecosystems such as Visual Studio Code, Sublime Text, PyCharm, Eclipse, and Atom. Administrators adapt configuration to orchestration platforms like Kubernetes, Mesos, and Nomad and to container registries used by Docker Hub and Google Container Registry. Customization practices draw on patterns from systems engineering at Facebook, Amazon, Alibaba Group, and Tencent Holdings Limited to enforce corporate policies, and mirror packaging policies employed by Red Hat and SUSE.

Comparison with alternatives

virtualenvwrapper is often compared to conda environments maintained by Anaconda, Inc., dependency-first tools like pipenv by Kenneth Reitz-led efforts, and modern project managers such as Poetry. Alternatives include language-agnostic tools like Docker and environment managers such as asdf and nvm for Node.js, or rbenv and rvm in the Ruby ecosystem. Organizations including Netflix, Google, and Instagram select tools based on requirements for binary distribution, platform support, and reproducible builds emphasized in infrastructures like Bazel and Buck.

Development history and maintenance

virtualenvwrapper originated in community discussions within the Python Software Foundation ecosystem and gained contributors from repositories hosted on services like GitHub and Bitbucket. Key maintainers and contributors have been active in broader open-source communities including Debian Project package maintainers, Ubuntu Developers, and volunteers from Arch Linux. Maintenance patterns follow governance and release practices similar to projects overseen by Apache Software Foundation, Linux Foundation, and NumFOCUS, with issue tracking and patches contributed by engineers from Mozilla, Canonical, Red Hat, and independent developers.

Category:Python (programming language) software