NEW htm-community forks: nupic.cpp, nupic.py

Thanks for creating the forks.

But the names are going to be a bit of a problem. nupic.cpp was nupic.core I assume. In that core there is the C++ core library itself and there will be clients interfaces for each of the languages. Initially a Python 3.x client, and then clients for C++, C++/clr and C# which I am working on. The name nupic.cpp kind of implies that this is just the C++ interface.

If you cannot use nupic.core would a better name for the core be nupic.lib, nupic.algorithms, or maybe nupic.community.core?