My first post was about Python ‘virtualenv
‘ – started with what is a virtual environment, why we need it, and a minimal example. The purpose was to clarify beginners about what they get to see in almost every Python example. After that I also wrote about pyenv
, and virualenvwrapper
, felt like I may have enhanced the confusion here, all the starters might be having the question – what’s the difference between pyenv, virtualenv, virtualenvwrapper ?
hence the today’s post title.
As you all know already that a virtual environment is ” a separate Python interpreter with its own set of installed packages.”
Continue reading “what’s the difference between pyenv, virtualenv, virtualenvwrapper”
After writing about ‘what is virtualenv
‘ and pyenv
I have been feeling a compulsion to write about the one remaining tool in the family i.e. virtualenvwrapper
As it is in the name, virtualenvwrapper is just a wrapper (an extension) around the virtualenv. The sole motive behind writing it, is covering the discrepancies or features virtualenv lacks, and biggest issue is managing these virtualenvs. As stated in the official docs, the main value-adding features of virtualenvwrapper are:
- Organizes all of the virtual environments at a single location.
- Provides better management of virtualenvs – intuitive commands for creating, deleting, copying virtualenvs.
- A single command to switch between environments i.e. workon (demonstrated later in the post)
- User-configurable hooks for all operations (see Per-User Customization).
- Plugin system for more creating shareable extensions (see Extending Virtualenvwrapper).
Continue reading “Better management of Python virtual environments with virtualenvwrapper”