Hello Marek, so if I want to stick with older version of bindings, for example the 0.3.1 i would run the installation command for that and then pip install nupic and everything should work? because right now I'm not sure if things are messed up because of some incomplete un-installations of older releases, or because of the problem of trying to install incompatible versions you mentioned. Thank you for the help!
have a nice day :) s. On Thu, Apr 21, 2016 at 3:12 PM, Marek Otahal <markota...@gmail.com> wrote: > Hi Sasha, > > nupic (python) and nupic.bindings(c++) have releases on PyPI, and all the > historical releases of the binaries are available, so you should always be > able to install both at any specific version you desire. > What you cannot do is running "latest" nupic and using an old > nupic.bindings; this is because the API changes from c++ have to be > reflected in the wrappers for python in nupic. > > Hope it helps your question. > Cheers, > Mark > > > On Thu, Apr 21, 2016 at 12:46 PM, Alexandra Vasilova < > alexandra.sasha.vasil...@gmail.com> wrote: > >> Hello! >> I am working with nupic on several computers and I want to make sure that >> the version I'm using is always the same - for debugging processes etc. >> Preferably I would like to use frozen version of nupic/bindings, one I >> can always rely on to remain the same. To avoid the situation that I run my >> installation script resulting in having two machines with different >> releases. (when I run script with bindings of version 0.3.1 for example >> now, I got an error that I should update) What is the best way to manage >> that? >> >> Thanks for the answer! >> Sasha >> >> > > > -- > Marek Otahal :o) > -- datapine GmbH Skalitzer Straße 33 10999 Berlin email: ka...@datapine.com
