This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
python:virtual_environments [2015/03/09 09:01] kauffman |
python:virtual_environments [2016/06/30 11:50] kauffman |
||
---|---|---|---|
Line 3: | Line 3: | ||
==== What and Why ==== | ==== What and Why ==== | ||
A Virtual Environment is a tool to keep the dependencies required by different projects in separate places, by creating virtual Python environments for them. It solves the “Project X depends on version 1.x but, Project Y needs 4.x” dilemma, and keeps your global site-packages directory clean and manageable. For example, you can work on a project which requires Django 1.3 while also maintaining a project which requires Django 1.0. ((http://docs.python-guide.org/en/latest/dev/virtualenvs)) | A Virtual Environment is a tool to keep the dependencies required by different projects in separate places, by creating virtual Python environments for them. It solves the “Project X depends on version 1.x but, Project Y needs 4.x” dilemma, and keeps your global site-packages directory clean and manageable. For example, you can work on a project which requires Django 1.3 while also maintaining a project which requires Django 1.0. ((http://docs.python-guide.org/en/latest/dev/virtualenvs)) | ||
+ | |||
+ | ==== Other things you should know ==== | ||
+ | https://github.com/pypa/virtualenv/pull/697 | ||
==== Using Virtual Environments ==== | ==== Using Virtual Environments ==== |