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.

2 files changed, 7 insertions, 5 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
diff --git a/setup.py b/setup.py
index e0932bf..ed8b514 100644
--- a/setup.py
+++ b/setup.py
@@ -43,7 +43,7 @@ setup(
  
     setup_requires = ['pyublas'],
     install_requires = ['uncertainties','pyzmq-static','spnav', 'pycuda', 
-                        'numpy', 'pygame', 'nose', 'sphinx'],
+                        'numpy>=1.6', 'pygame', 'nose', 'sphinx'],
     test_suite = 'nose.collector',
     
 )