Trying to get NuPIC installed on the machine mentioned above. It’s a shared machine, so I’m installing under my home account directory without root access.
I’ve set up my own installation of Python 2.7.12 under my home directory with pycapnp, numpy, setuptools, wheel, cython and pip all installed properly and working. All are the latest versions available.
I’ve installed CMake 3.5.1 under my home directory and its working fine.
I’ve tried “pip install nupic” and “pip install nupic --user” and they both result in this error when trying to install nupic.bindings:
Could not find a version that satisfies the requirement nupic.bindings==1.0.0 (from nupic) (from versions: 1.0.1)
No matching distribution found for nupic.bindings==1.0.0 (from nupic)
When trying to run “pip install nupic.bindings” and “pip install nupic.bindings --user” I get the following error:
Complete output from command python setup.py egg_info:
Setup SWIG Python module
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/tmp/pip-build-n5QNa_/nupic.bindings/setup.py", line 212, in <module>
version=getVersion(),
File "/tmp/pip-build-n5QNa_/nupic.bindings/setup.py", line 48, in getVersion
with open(os.path.join(REPO_DIR, "VERSION"), "r") as versionFile:
IOError: [Errno 2] No such file or directory: '/tmp/VERSION'
----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-n5QNa_/nupic.bindings/
I’ve also tried installing the nupic core from the .whl files located at https://pypi.python.org/pypi/nupic.bindings. Specifically, I tried running “pip install nupic.bindings-1.0.2-cp27-cp27mu-manylinux1_x86_64.whl” which results in the following error:
nupic.bindings-1.0.2-cp27-cp27mu-manylinux1_x86_64.whl is not a supported wheel on this platform.
Regarding the /tmp/VERSION error, I just ran into that as well. Turns out that when installing nupic.bindings separately, only the bindings directory of the nupic.core repository is cloned. The setup script for nupic.bindings moves up two directories to find the VERSION file in what it thinks is /tmp/nupic.core, but is actually just /tmp (as only a subdir of nupic.core was cloned)
I cheaply fixed this by manually adding the /tmp/VERSION file, however later on it also fails to find nupic.bindings/requirements.txt, which, despite being in the bindings subdir, isn’t cloned at all either. I’m not too familiar with the inner workings of pip, but it seems to me it’s cloning some wrong version of nupic.bindings.
Interesting…It seems I’m also unable to force install a different version of nupic.bindings…the only available version reported by pip is 1.0.1. I wonder if installing from source might mitigate that.
I’m not able to install nupic.bindings successfully from source either.
bjk4704@doors:~/nupic.core$ nupic-bindings-check
terminate called after throwing an instance of 'std::runtime_error'
what(): initializeNumpy: numpy.core.multiarray failed to import.
Aborted (core dumped)
For anybody reading in the future, I did manage to get NuPIC installed on the machine. It seems the bug for me was that there was conflicting versions of Python installed which resulted in the above errors. After resolving that, I was able to run simply “pip install nupic --user” without even building nupic.bindings first or building from source at all and all installed correctly and is tested working properly.
Hooray! I have found the python language very nice, but the python development / runtime environment extremely unstable and brittle (especially on a mac).
@bkutt Hey, I got the same issue running on ubuntu 16.04!
Do you know which python versions were conflicting?
My environment variable points to 2.7 python default version. However there are multiple installed (all symlinks listed):
