On Thu, 2014-05-29 at 12:37 -0400, Alan Conway wrote: > My concern is that as the boundary of interaction grows it will become > complicated and error-prone to maintain hand-written wrappers. E.g. look > at router_pynode.c. It's a lot of hand-written call-Python-from-C code > to generate a python class view of a C API. I suspect that a thin swig > wrapper between clean Python code and a clean C API would be easier to > understand and maintain thank this C/Python mish-mash. (I might be > wrong, if I am I won't do it :)
cffi looks quite promising: it's basically C-in-python rather than python-in-C which is the right way around IMO. It lets us skip the SWIG wrapper and go straight from python to C in a fairly clean way. Hmm... --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
