Hi Sasha,
On Fri, Apr 22, 2016 at 10:56 AM, Karin Valisova <[email protected]> wrote: > 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? > No, `pip install nupic` uses the latest release of nupic, which is likely incompatible with your chosen older bindings version. You'll need to specify relevant nupic version as well: $ pip install nupic==xxx Downloading/unpacking nupic==xxx Could not find a version that satisfies the requirement nupic==xxx (from versions: 0.2.3, 0.1.2, 0.3.1, 0.2.8, 0.3.6, 0.2.2, 0.4.5, 0.5.2, 0.3.5, 0.5.0, 0.0.36, 0.4.2, 0.2.9, 0.3.6, 0.2.10, 0.2.11, 0.2.12, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.5.0, 0.5.1, 0.5.2, 0.0.32.linux-x86_64, 0.0.32.macosx-10.9-intel, 0.0.32, 0.0.33.linux-x86_64, 0.0.33.macosx-10.9-intel, 0.0.33, 0.0.34, 0.0.35, 0.0.37, 0.0.38, 0.1.0, 0.1.1, 0.1.3, 0.2.0, 0.2.1, 0.2.10, 0.2.11, 0.2.12, 0.2.4, 0.2.5, 0.2.6, 0.2.8, 0.2.9, 0.3.0, 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.4.5, 0.5.1) I'm not sure how to find matching versions, but it would make sense if nupic==0.3.1 were compatible with nupic.bindings==0.3.1 (?) > 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. > Messy installations can complicate the process, I suggest you try to get rid of any nupic{.bindings} installations and start from scratch. Hope that helps. Have a nice day, > Thank you for the help! > > have a nice day :) > s. > > > > > On Thu, Apr 21, 2016 at 3:12 PM, Marek Otahal <[email protected]> > 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 < >> [email protected]> 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: [email protected] > -- Marek Otahal :o)
