Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

swig vs. pybind11? #30

Open
dan-stromberg opened this issue May 30, 2019 · 1 comment
Open

swig vs. pybind11? #30

dan-stromberg opened this issue May 30, 2019 · 1 comment

Comments

@dan-stromberg
Copy link

Can someone please help me understand why the community edition is abandoning swig for pybind11?

pybind11 is probably nicer for Python, but I suspect it won't work well for other languages.

Also, it seems like switching to pybind is a pretty large change that may even have implications for the API. Would it make sense to migrate to pybind After the switch to python 3.x?

Was there a real show-stopping bug or missing feature preventing the continued use of swig?

Thanks!

@breznak
Copy link

breznak commented May 30, 2019

You could ask directly here https://github.com/htm-community/nupic.cpp/issues

Was there a real show-stopping bug or missing feature preventing the continued use of swig?

i think one of the main reasons was Windows & Python 3, both ready now in community.
Also, pybind11 is much nicer to write bindings.

but I suspect it won't work well for other languages.

likely, in our survey noone really cared about other languages, people wanted either python + c++ backend, or c++. There's also native Java, pytorch,..repos.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants