Difference between revisions of "Using virtualenv"

From mn/bio/cees-bioinf
Jump to: navigation, search
 
Line 9: Line 9:
 
<pre>cd my_python_dir
 
<pre>cd my_python_dir
 
./bin/activate</pre>
 
./bin/activate</pre>
And you're ready to go. Deactivating the environment
+
And you're ready to go.
<pre>deactivate</pre>
+
 
 
This is a fix necessary for abel and the cod nodes, normally not necessary:
 
This is a fix necessary for abel and the cod nodes, normally not necessary:
 
<pre>unset PYTHONPATH</pre>
 
<pre>unset PYTHONPATH</pre>
 +
Deactivating the environment
 +
<pre>deactivate</pre>
 
==== Using an existing virtual env ====
 
==== Using an existing virtual env ====
 
<pre>cd my_python_dir
 
<pre>cd my_python_dir
 
./bin/activate</pre>
 
./bin/activate</pre>
 +
==== Installing modules in your virtualenc ====
 +
 +
Activate and then run
 +
<pre>pip install module_name</pre>

Latest revision as of 12:22, 16 June 2015

virtualenv is a tool to create isolated Python environments. See https://virtualenv.pypa.io/en/latest/index.html

Setting up virtualenv on the cod-nodes/abel

module load python2
virtualenv my_python_dir

will create locally a python tree.

Then you can run

cd my_python_dir
./bin/activate

And you're ready to go.

This is a fix necessary for abel and the cod nodes, normally not necessary:

unset PYTHONPATH

Deactivating the environment

deactivate

Using an existing virtual env

cd my_python_dir
./bin/activate

Installing modules in your virtualenc

Activate and then run

pip install module_name