summaryrefslogtreecommitdiff
path: root/doc/source
diff options
context:
space:
mode:
authorStan Seibert <stan@mtrr.org>2011-11-17 15:34:07 -0500
committertlatorre <tlatorre@uchicago.edu>2021-05-09 08:42:38 -0700
commitf9a4ae2b14b2b95611fc73541e6ab864ffddd533 (patch)
treec03b24aa6e21ec8c86f31b5c1415b237ec03be41 /doc/source
parentaa9bf67f31adc424d1d24ab1186026c1754ea00c (diff)
downloadchroma-f9a4ae2b14b2b95611fc73541e6ab864ffddd533.tar.gz
chroma-f9a4ae2b14b2b95611fc73541e6ab864ffddd533.tar.bz2
chroma-f9a4ae2b14b2b95611fc73541e6ab864ffddd533.zip
Nope, Chroma really does require Numpy 1.6 or later. Putting dependency back and including in installation guide the workaround to get numpy to install.
Diffstat (limited to 'doc/source')
-rw-r--r--doc/source/install.rst10
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/source/install.rst b/doc/source/install.rst
index 150fb38..4c3e439 100644
--- a/doc/source/install.rst
+++ b/doc/source/install.rst
@@ -269,13 +269,15 @@ to create a file in your ``$HOME`` directory called
BOOST_LIB_DIR = ['/usr/lib64']
BOOST_PYTHON_LIBNAME = ['boost_python-mt-py27']
-Now we at a stage where the automatic dependency resolution features
-of ``pip`` can do their magic. We need to upgrade the distribute
-module and install PyUblas prior to installation, but the rest should
-be automatic::
+Some of the python dependencies of Chroma have fiddly installation
+scripts, so we need to add them individually before doing the final
+install of the Chroma package::
pip install -U distribute
pip install pyublas
+ # Bug workaround for Numpy 1.6.1
+ mkdir $VIRTUAL_ENV/local
+ ln -s $VIRTUAL_ENV/lib $VIRTUAL_ENV/local/lib
pip install -e hg+http://bitbucket.org/chroma/chroma#egg=Chroma
Now you can enable the Chroma environment whenever you want by typing