Here's a summary of of comments that have come up in chat: - Andrej recommended using PyBind11, a close cousin to boost.python. it comes recommended by Sebastian Koslowski also. It's only a few headers and we could ship it as part of the source tree. - The question arose if we even need the python bindings as part of the standard install. Personally I think we do, installing GNU Radio from source should simply give you all the features. But it's a good thing to discuss. - Another comment was that we could simply have c bindings and then use those for python. The general consensus around that was that we can treat the C++/Python interface specially, given its importance and tradition. C bindings can be discussed separately.
-- M On Thu, 27 Dec 2018, 13:58 Martin Braun <mar...@gnuradio.org wrote: > Hi all, > > https://github.com/gnuradio/greps/blob/master/grep-0015-remove-swig.md > > this might be the craziest GREP yet: How about we kill SWIG as a > dependency? Note: We don't want to remove functionality, and we love our > Python bindings. But, could we do better? SWIG slows down our compilers, > creates hundreds of kB of source code, and we don't really know what it > does. > On the other hand, that's because it solves a very complex problem: We > point it at headers, and it auto-creates Python libraries for us. > And of course, changing this would most likely cause some code to become > no longer compatible with GNU Radio. > > Discuss! > > -- Martin > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
