Differences

This shows you the differences between two versions of the page.

--- python:virtual_environments [2015/03/08 23:17] – adding common usage kauffman
+++ python:virtual_environments [2016/06/30 11:50] – kauffman
@@ Line 3: / Line 3: @@
 ==== 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))
+==== Other things you should know ====
+https://github.com/pypa/virtualenv/pull/697
 ==== Using Virtual Environments ====
@@ Line 91: / Line 94: @@
 (exampleproject)user@computer:~/projects/exampleproject$ deactivate
 user@computer:~/projects/exampleproject$
-</code>
-====== virtualenvwrapper ======
-virtualenvwrappers goal is to make virtualenv easier to use... sort of like when iTunes automatically organizes your iTunes library.
-==== Basic Usage ====
-=== Create a virtual environment ===
-This creates the exampleproject folder inside ~/Envs.
-<code>
-user@computer:~/$ mkvirtualenv venv
-</code>
-=== Work on a virtual environment ===
-'virtualenvwrapper' provides tab-completion on environment names. It really helps when you have a lot of environments and have trouble remembering their names.
-'workon' also deactivates whatever environment you are currently in, so you can quickly switch between environments.
-<code>
-user@computer:~/$ workon venv
-</code>
-Deactivating is still the same:
-<code>
-user@computer:~/$ deactivate
-</code>
-To delete:
-<code>
-user@computer:~/$ rmvirtualenv venv
-</code>
-=== Other useful commands ===
-<code>
-lsvirtualenv
-  List all of the environments.
-cdvirtualenv
-  Navigate into the directory of the currently activated virtual environment,
-  so you can browse its site-packages, for example.
-cdsitepackages
-  Like the above, but directly into site-packages directory.
-lssitepackages
-  Shows contents of site-packages directory.
 </code>