Create isolated Python environments with ease using our Virtual Python Environment builder software.
As a software review, I want to share my thoughts on virtualenv-distribute. This tool is a fork of the virtualenv utility, but uses distribute instead of the setuptools package. The virtualenv-distribute fork was initiated by Philip Jenvey and is now maintained by Florian Schulze.
Virtualenv, on the other hand, is an extension of virtual-python and a successor to workingenv. Developed by Ian Bicking, this tool is sponsored by the Open Planning Project and licensed under an MIT-style permissive license. It is easy to install virtualenv-distribute with the command "easy_install virtualenv-distribute" or from the subversion repository using "easy_install virtualenv==dev".
Essentially, virtualenv is designed to create isolated Python environments to deal with dependencies and versions, and indirectly permissions. For instance, if you have an application that requires version 1 of LibFoo while another needs version 2, how would you use both these applications? If everything is installed into /usr/lib/python2.4/site-packages, you may accidentally upgrade an application that shouldn't be updated.
The tool creates a unique environment that has its own installation directories without sharing libraries with other virtualenv environments that ideally doesn't use globally installed libraries either. To use virtualenv, you only need to run "python virtualenv.py ENV" or "virtualenv ENV" after installation. This creates ENV/lib/python2.x/site-packages, where installed libraries will go. It also installs distribute and creates ENV/bin/python, a Python interpreter that uses this environment. Whenever you use that interpreter or a script that has #!/path/to/ENV/bin/python in it, the libraries in that environment will be used. For Windows users, scripts and executables will go to ENVScripts and bin/ is replaced with Scripts.
In summary, virtualenv-distribute is a useful tool that creates a secure and isolated Python environment that restricts dependency confusion and version conflicts. It is easy to install and use, and is particularly helpful when installing applications and leaving them be.
Virtualenv, on the other hand, is an extension of virtual-python and a successor to workingenv. Developed by Ian Bicking, this tool is sponsored by the Open Planning Project and licensed under an MIT-style permissive license. It is easy to install virtualenv-distribute with the command "easy_install virtualenv-distribute" or from the subversion repository using "easy_install virtualenv==dev".
Essentially, virtualenv is designed to create isolated Python environments to deal with dependencies and versions, and indirectly permissions. For instance, if you have an application that requires version 1 of LibFoo while another needs version 2, how would you use both these applications? If everything is installed into /usr/lib/python2.4/site-packages, you may accidentally upgrade an application that shouldn't be updated.
The tool creates a unique environment that has its own installation directories without sharing libraries with other virtualenv environments that ideally doesn't use globally installed libraries either. To use virtualenv, you only need to run "python virtualenv.py ENV" or "virtualenv ENV" after installation. This creates ENV/lib/python2.x/site-packages, where installed libraries will go. It also installs distribute and creates ENV/bin/python, a Python interpreter that uses this environment. Whenever you use that interpreter or a script that has #!/path/to/ENV/bin/python in it, the libraries in that environment will be used. For Windows users, scripts and executables will go to ENVScripts and bin/ is replaced with Scripts.
In summary, virtualenv-distribute is a useful tool that creates a secure and isolated Python environment that restricts dependency confusion and version conflicts. It is easy to install and use, and is particularly helpful when installing applications and leaving them be.
What's New
Version 1.3.4.4 / 1.3.5dev-1: N/A