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”
You may be a mid-level Python programmer using Python 2.7.5 for sometime, but also curious about Python 3.x.x, or check for yourself what is this all the Python 2 vs 3 debate over Internet, or simply the new functionalities or conventions being introduced in Python 3.x.x. or, just a Python newbie starting off and all so confused given the Python version debate. Don’t worry, my friends you have been rescued – you can keep multiple versions of Python (as many as you like).
There may be lot ways to install multiple Python versions, in the post I’ll be focusing on doing it using penv. – as it’s the most elegant way to do so.
Continue reading “pyenv – managing multiple Python versions”
For the starter (this is the opening post for the devopspy.com) let’s start with something basic, something confusing, something you see in almost every python code example i.e. virtual environment.
Python is an interpreted language, and for development all we need is a Python interpreter (included in Linux based OS – for Windows can be installed using the provided .msi). Like other programming languages Python has its own way of enhancements i.e. to use functionality not there by default, all we have to do is install the package, using any installation utility – pip (most common way), easy_install, or manual installation. These installed packages may termed as the requirements or the dependencies. These dependencies vary for every project – to get a project working all we need is the environment setup ( i.e. Python and the dependencies installed).
What is a virtual environment ?
is basically a separate Python interpreter with its own set of installed packages. As mentioned above the Python interpreter along with the installed packages make the environment – so we can have multiple Python environments on a single machine, the environments other the default are termed as virtual environment, which we need to create and activate before we can use (demonstrated later).
Continue reading “What is virtualenv, why we need it”