python:virtual_environments
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
python:virtual_environments [2014/11/25 14:14] – kauffman | python:virtual_environments [2016/06/30 11:56] (current) – [Other things you should know] kauffman | ||
---|---|---|---|
Line 4: | Line 4: | ||
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:// | 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:// | ||
+ | ==== Other things you should know ==== | ||
+ | - https:// | ||
+ | - http:// | ||
==== Using Virtual Environments ==== | ==== Using Virtual Environments ==== | ||
The python virtual environment package is installed by default on most CS machines. To make sure you can do the following: | The python virtual environment package is installed by default on most CS machines. To make sure you can do the following: | ||
Line 33: | Line 36: | ||
==== Activate ==== | ==== Activate ==== | ||
- | Now you need to activate your virtual environment. This will setup some path variables to make the evironments | + | Now you need to activate your virtual environment. This will setup some path variables to make the environments |
< | < | ||
user@computer: | user@computer: | ||
(exampleproject)user@computer: | (exampleproject)user@computer: | ||
- | </ | ||
- | ==== Deactivate ==== | ||
- | To deactivate or stop working on your environment use the fuction that gets sourced when you activate your environment: | ||
- | < | ||
- | (exampleproject)user@computer: | ||
- | user@computer: | ||
</ | </ | ||
- | ====== virtualenvwrapper ====== | + | ==== Installing Modules |
- | virtualenvwrappers goal is to make virtualenv easier to use... sort of like when iTunes automatically organizes your iTunes library. | + | After activating the virtual environment you will notice that your prompt changed a little. This is not the only thing that has changed. Your $PATH and default python have changed as well (just checkout the bin/ |
- | ==== Basic Usage ==== | + | Notice that the ' |
- | === Create a virtual environment | + | |
- | This creates | + | |
< | < | ||
- | user@computer: | + | (exampleproject)user@computer: |
+ | / | ||
</ | </ | ||
- | |||
- | === Work on a virtual environment === | ||
- | ' | ||
- | ' | ||
< | < | ||
- | user@computer: | + | (exampleproject)user@computer: |
+ | / | ||
+ | </ | ||
+ | < | ||
+ | (exampleproject)user@computer: | ||
+ | / | ||
</ | </ | ||
- | Deactivating is still the same: | + | So to actually install your own python modules you can use ' |
< | < | ||
- | user@computer: | + | (exampleproject)user@computer: |
+ | Downloading/ | ||
+ | Downloading docopt-0.6.2.tar.gz | ||
+ | Running setup.py egg_info for package docopt | ||
+ | |||
+ | Installing collected packages: docopt | ||
+ | Running setup.py install for docopt | ||
+ | |||
+ | Successfully installed docopt | ||
+ | Cleaning up... | ||
</ | </ | ||
- | To delete: | + | |
+ | Notice where docopt was installed (~/ | ||
< | < | ||
- | user@computer: | + | (exampleproject)user@computer: |
+ | -rw------- 1 user group 19946 Mar 8 23:12 local/ | ||
+ | -rw------- 1 user group 26140 Mar 8 23:12 local/ | ||
+ | |||
+ | local/ | ||
+ | total 40 | ||
+ | -rw------- 1 user group 1 Mar 8 23:12 dependency_links.txt | ||
+ | -rw------- 1 user group 86 Mar 8 23:12 installed-files.txt | ||
+ | -rw------- 1 user group 21525 Mar 8 23:12 PKG-INFO | ||
+ | -rw------- 1 user group 651 Mar 8 23:12 SOURCES.txt | ||
+ | -rw------- 1 user group 7 Mar 8 23:12 top_level.txt | ||
</ | </ | ||
- | === Other useful commands | + | |
+ | ==== Deactivate | ||
+ | To deactivate or stop working on your environment use the function that gets sourced when you activate your environment: | ||
< | < | ||
- | lsvirtualenv | + | (exampleproject)user@computer: |
- | List all of the environments. | + | user@computer: |
- | cdvirtualenv | + | |
- | Navigate into the directory of the currently activated virtual environment, | + | |
- | so you can browse its site-packages, | + | |
- | cdsitepackages | + | |
- | Like the above, but directly into site-packages directory. | + | |
- | lssitepackages | + | |
- | Shows contents of site-packages directory. | + | |
</ | </ |
/var/lib/dokuwiki/data/pages/python/virtual_environments.txt · Last modified: 2016/06/30 11:56 by kauffman