Then, we can go a new PR with @hellerm 's changes for the redux dependencies.

Thoughts? @hellerm, @chhening

Yeah, that can wait. They’re included for now. Maybe we can include that in the scope of general CMake changes? We can do a lot to reduce the complexity of the CMake scripts. I have a few question on the matter, but that should be a different thread.

@chhenning what is your feeling about our tries to integrate the pybind in the repo so far?
I think we got diverged and are now solving issues of {repo structure, platform support, dependency management}*.

Our target here was to introduce pybind, ideally replace SWIG, make Regions use pybind functionality.
Should we try to do that with minimal changes?

Not really. @breznak wanted to open a new pull request based on what I wrote:

chhenning:

@breznak Here is my thinking of what we should do. 1. Incorporate my nupic.core code changes. Ideally copy over /src/nupic and /src/test with my code. You can take src from here You can do that on separate branch or a new repo. Add pybind11 to /include It doesn’t matter what python you have on you system. 2. Compile nupic.core and only that. Don’t think about the python bindings modules. You will have to adapt the cmake script. Some cpp files are deleted (think old python c api wrapper cl…

I just found this thread and checked out your git repo. Looks like you’ve made some great progress on porting to Python 3. The last update in the Git repo seems to be about 2 months ago. Is active development still ongoing?