Getting started with the OpenHatch code (moved): Difference between revisions

No more virtualeenv
imported>Paulproteus
m (Protected "Getting started with the OpenHatch code" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite)))
imported>Paulproteus
(No more virtualeenv)
Line 37:
It contains instructions you need to follow. Go ahead and do that. I can wait.
 
 
== Problems with buildout? ==
 
If you have an error like: ImportError: No module named enthought
 
Then you probably need to wrap your environment with virtualenv. This will insulate it against libraries you have installed on your system.
 
Instructions for setting up a virtualenv wrapper:
 
<pre>
sudo apt-get install virtualenvwrapper python-setuptools
</pre>
 
Be sure to configure your shell so that pip knows where to find your virtual environments:
 
<pre>
# in .bashrc or .bash_profile
source /etc/bash_completion.d/virtualenvwrapper
</pre>
 
Once installed, create your virtual environment for OpenHatch and install the dependencies
 
<pre>
cd oh-mainline
mkvirtualenv --no-site-packages openhatch
mkdir ~/.virtualenvs
### use this command
##### workon openhatch
### only if your prompt hasn't got (openhatch)user@host:~/oh-mainline/$
python bootstrap.py
deactivate
</pre>
 
That ''bootstraps'' your environment so that it will always use the virtualenv. Now, just run:
 
<pre>
./bin/buildout
</pre>
 
And you should be fine. All future commands from ./bin/* will safely use the virtualenv and ignore Python modules installed systme-wide. (FIXME: Make ''sure'' this is true!)
 
== Run the tests ==
Anonymous user