When the redesign efforts are more stable, I'm looking at a SWIG-based
wrapper approach. Among the targets that seem interesting thus far are
Python, Java, C++, C#, etc. That to say, you're free to consider
hand-spun bindings; however, SWIG will offer build-driven bindings.
When changes happen to the underlying code, a SWIG build will yield
the bindings as well. At least that's my plan/contribution.
On Fri, Aug 4, 2017 at 3:51 AM, Cees Wesseling <ceeswesseling@xxxxxxxxx> wrote:
Hi there,
nanomsg seems to be a perfect for my development requirements, so I just
started studying it.
On the documentation page there are 3 Python bindings listed, with
nanomsg-python tagged as recommended. I like to know the rationale why that
one is recommended. Second if there are any people on this list that have
experience with or researched multiple Python binding projects and their
opinion.
IMHO, I like the idea of nnpy being an autowrapper with cffi. But maybe
nanomsg-python has some advantage over simply wrapping.
Thanks, Cees
