I couldn't agree with this more. Though NPC-56 comes naturally if one has a tight c++ library with support for language bindings. Typically language communities with see to the packaging thereof.
>From my POV I'd go as far as to impose order on the list by saying (after >cmake) the next important step is strip to the core and make it easy for >bindings. Portability allows other communities to access NuPIC thus our community grows. Greg Slepak raises important points especially regarding the use of environment variables. Kind regards Stewart >In no particular order: > >NPC-56 Investigate the feasibility of making nupic installable through >pip and/or easy_install (https://issues.numenta.org/browse/NPC-56) >NPC-205 Create C++ examples that don't use Python >(https://issues.numenta.org/browse/NPC-205) >NPC-230 pip command fails, but build is erroneously proclaimed as >successful (https://issues.numenta.org/browse/NPC-230) >NPC-290 Get language bindings working for C++ CLA model >(https://issues.numenta.org/browse/NPC-290) >NPC-390 Resolve dependency management issues >(https://issues.numenta.org/browse/NPC-390) >NPC-308 Remove external dependencies from NuPIC repo >(https://issues.numenta.org/browse/NPC-308) >NPC-120 Modular design, remove static libs >(https://issues.numenta.org/browse/NPC-120) >NPC-274 Create a language-independent checkpoint/serialization format >for the CLA (https://issues.numenta.org/browse/NPC-274) _______________________________________________ nupic mailing list [email protected] http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org
